Skip to main content
Glama

Delimit X Fetch

delimit_x_fetch

Fetch tweets directly by status ID or full X/Twitter URL. Pulls one or many tweets in a single batch using cached reads, so repeated lookups are free.

Instructions

Fetch tweets from X by id or URL via twttr241 RapidAPI (LED-825).

When to use: to surgically fetch one or many tweets by id/URL, sharing the cached path with delimit_social_target so repeats are free. When NOT to use: to scan for new content (use delimit_social_target) or fetch a Reddit thread (delimit_reddit_fetch_thread).

Sibling contrast: delimit_social_target scans for opportunities; delimit_reddit_fetch_thread is the Reddit equivalent; this is the X (Twitter) single/batch fetcher.

Side effects: read-only network call via twttr241 (RapidAPI). Inherits the LRU + SQLite cache + budget gate from the social-target scanner — repeated reads are free. No writes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoComma-separated list of status ids OR URLs for a batch fetch. Each is normalized to a status id and fetched independently.
id_or_urlNoSingle status id ("2048825010371039648") OR a full x.com / twitter.com URL — id is extracted automatically. Mutually exclusive with `ids`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.7.9

TDQS

A3.7/5.0
Behavior1/5

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

The description explicitly claims 'read-only network call' and 'No writes', but the annotations set readOnlyHint to false, which implies the tool is not marked read-only. This is a direct annotation contradiction, and the description's 'No writes' also conflicts with its own mention of an SQLite cache that presumably writes to disk.

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

Conciseness4/5

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

The description is well structured with clear sections and the most important information is front-loaded. It is slightly verbose due to ticket references and repeated sibling contrast, but every section earns its place and the format is easy for an agent to parse.

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?

The description covers purpose, when to use, alternatives, side effects, caching, and budget behavior, and an output schema is present. It is complete enough for an agent to invoke correctly, though the read-only contradiction with annotations prevents a perfect score.

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 description coverage is 100%, and both parameters have detailed descriptions including mutual exclusivity and normalization behavior. The tool description adds no parameter-level detail beyond restating 'by id or URL', so the schema already does the heavy lifting.

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 opens with a specific verb and resource ('Fetch tweets from X by id or URL') and explicitly names the integration. The sibling contrast further clarifies exactly what this tool is and is not, making it easy for an agent to distinguish from delimit_social_target and delimit_reddit_fetch_thread.

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?

The description has explicit 'When to use' and 'When NOT to use' sections, naming the exact alternative tools and the conditions that should route to them. This gives the agent clear decision criteria without needing to infer anything.

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

Deploy Server

Other Tools