> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/start-with-an-ai-agent/docs-search.md).

# Search and read help

Search and read published Blotato help through the documentation MCP endpoint, separately from account access and publishing tools.

Use the [task index](/start-with-an-ai-agent/agents.md#choose-a-task) when the outcome is known. For another question, search published help pages through the documentation MCP server. This is an optional lookup route, not another requirement for publishing.

## Choose the server

| Purpose                             | Server                                                              | Access                                                                                 |
| ----------------------------------- | ------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| Look up published help              | [Documentation MCP endpoint](https://help.blotato.com/~gitbook/mcp) | Public documentation. No Blotato API key or account authorization required.            |
| Work with connected social accounts | `https://mcp.blotato.com/mcp`                                       | Follow [client setup](/start-with-an-ai-agent/mcp/setup.md) and verify account access. |

The documentation server does not connect social accounts or publish posts. Its results describe published documentation, not unpublished repository edits.

## Find the answer

1. Add the documentation endpoint to an HTTP MCP client under a distinct name such as `blotato-docs`, if a docs connection is needed.
2. Discover its tools with `tools/list`.
3. Call `searchDocumentation` with a `query` string.
4. Select a result for the customer's surface: API/MCP execution or Blotato website instructions.
5. Call `getPage` with the result's page URL in `url`.
6. Read the page before answering or constructing a request.

| Tool                  | Input   | Use                                            |
| --------------------- | ------- | ---------------------------------------------- |
| `searchDocumentation` | `query` | Retrieve matching help-page excerpts and URLs. |
| `getPage`             | `url`   | Retrieve the selected page's Markdown.         |

Example search input:

```json
{"query":"schedule timezone"}
```

A search result about a website button is not an API parameter reference. A result about API scheduling is not a website walkthrough. Search rank alone does not establish relevance or correctness. Follow the [task index](/start-with-an-ai-agent/agents.md#choose-a-task) when results mix surfaces.

Keep API keys and customer data out of documentation queries. Use search and page retrieval for lookup. The server also advertises `askQuestion` and `sendFeedback`. Feedback sends a report, so require the user's request before using it.

## Without a docs MCP connection

1. Read the [task index](/start-with-an-ai-agent/agents.md#choose-a-task) or [documentation index](https://help.blotato.com/llms.txt).
2. Fetch the selected page as Markdown by appending `.md` to its published URL.

For account actions, return to [Blotato client setup](/start-with-an-ai-agent/mcp/setup.md). Reading help documentation does not verify access to a customer's connected accounts.

The hosted documentation endpoint is provided by GitBook. See [GitBook's published-docs MCP requirements](https://gitbook.com/docs/ai-for-your-readers/mcp-servers-for-published-docs).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.blotato.com/start-with-an-ai-agent/docs-search.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.