Retrieve HTML body of a Tilda page without for quick preview. Optionally fetch only metadata to save context.
Получить только тело страницы Tilda (HTML без ; ссылки на Tilda CDN) — для быстрого чтения/preview. metadata_only=true — без html/css/js.
| Name | Required | Description | Default |
|---|---|---|---|
| pageid | Yes | ID страницы Tilda | |
| metadata_only | No | Если true — вернуть только метаданные страницы без html/css/js (экономит контекст) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries behavioral disclosure. It states what is returned (HTML body, or metadata with flag) but omits error handling, authentication needs, or side effects. Acceptable for a simple read tool, but could be more complete.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences covering the main purpose and a key parameter option. No extraneous content, front-loaded with the core action. Extremely concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity and full schema coverage, the description adequately covers what the tool does and how to modify behavior via parameters. It lacks output schema details and explicit sibling differentiation, but overall complete for expected usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with clear descriptions for both parameters. The description restates the metadata_only effect but adds no new semantic meaning beyond what the schema already provides. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description specifies the tool retrieves the body of a Tilda page (HTML without <head>, with Tilda CDN links) for quick reading/preview, clearly distinguishing it from potentially fetching the full page. The verb 'get' and resource 'page body' are explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for quick reading/preview and explains the metadata_only flag for context saving, but it does not explicitly contrast with sibling tools like get_page or provide when/why to choose this tool over alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/theYahia/tilda-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server