Skip to main content
Glama

get_twitterapi_guide

Retrieve the full content of any TwitterAPI.io documentation page by page key. Access headers, paragraphs, and code examples for offline reading or integration.

Instructions

Get a TwitterAPI.io page from the offline snapshot by page key.

USE THIS WHEN: You need the full content of a specific page (guides, docs, policies, contact, etc.). TIP: Use search_twitterapi_docs if you don't know the page key.

RETURNS: Full guide content with headers, paragraphs, and code examples.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guide_nameYesPage key (from data/pages). Examples: pricing, qps_limits, privacy, contact, introduction, authentication.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
titleNo
headersNo
markdownYes
raw_textNo
guide_nameYes
list_itemsNo
paragraphsNo
descriptionNo
code_snippetsNo
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It mentions 'offline snapshot' but does not explain staleness, authentication needs, or read-only nature. Lacks depth.

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

Conciseness5/5

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

Three sentences: action, usage guidance, return info. Front-loaded, no wasted words. Efficiently conveys essential information.

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

Completeness4/5

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

Given simple tool with one parameter, schema covers all options, output schema exists. Description mentions return content format. Minor lack of clarity on 'offline snapshot' implications.

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 has 100% coverage with enum and description, so baseline is 3. The description adds example values but no additional semantics beyond the schema.

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 it retrieves a TwitterAPI.io page from an offline snapshot by page key, using specific verb and resource. It distinguishes from sibling by advising use of search_twitterapi_docs for unknown keys.

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

Usage Guidelines5/5

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

Explicitly states when to use: for full content of a specific page. Provides alternative tool when page key is unknown, offering clear context.

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/dorukardahan/twitterapi-io-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server