Skip to main content
Glama

get_page_export_body

Export Tilda page body (without ) with localized assets for integration into your CMS or custom template. Optionally retrieve only metadata to save context.

Instructions

Экспорт тела страницы Tilda с локализованными ассетами {from,to} (без ) — для вставки в свой шаблон/CMS. metadata_only=true — без html/css/js.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageidYesID страницы Tilda
metadata_onlyNoЕсли true — вернуть только метаданные страницы без html/css/js (экономит контекст)
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It discloses the output excludes the <head>, includes localized assets, and describes the metadata_only behavior. This provides useful behavioral context beyond the input schema, though it omits details like response format or potential side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively concise but contains unclear curly brace notation '{from,to}' which may mislead agents. It front-loads the main purpose but could be more structured and remove ambiguous elements.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description partially explains the return (body without head) but does not specify format (e.g., HTML string). It also fails to clearly differentiate from sibling get_page_body or explain the apparent localization parameters. Some gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description rephrases the metadata_only parameter semantics but adds no new meaning for pageid. The notation '{from,to}' in the description is confusing and not reflected in the schema, detracting from clarity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool exports the body of a Tilda page with localized assets, without the <head>, for insertion into a template/CMS. It specifies the verb 'export' and resource 'page body', and the mention of localization distinguishes it from siblings like get_page_body.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description indicates when to use the tool (for inserting into a template/CMS) and explains the metadata_only flag for returning only metadata (economizing context). It does not explicitly list alternative tools or when not to use it, but the usage context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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