Skip to main content
Glama
zezeron
by zezeron

Batch Fetch Tweets

tweetsave_batch
Read-onlyIdempotent

Fetch up to 10 tweets at once by providing their URLs or IDs, outputting in markdown or JSON format.

Instructions

Fetch multiple tweets at once (max 10).

Useful for:

  • Collecting tweets from a list

  • Building a feed from multiple sources

  • Comparing multiple tweets

Args:

  • urls (string[]): Array of tweet URLs or IDs (max 10)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Array of tweets or a combined feed in markdown format.

Examples:

  • "Fetch these tweets: [url1, url2, url3]"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesArray of tweet URLs or IDs (max 10)
response_formatNoOutput format: 'markdown' or 'json'markdown
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive; description adds batch limit and output format details, consistent with annotations.

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?

Extremely concise: single sentence for purpose, bullet list for use cases, then args/returns/examples; no wasted words.

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?

Describes return as 'Array of tweets or a combined feed in markdown format' which is acceptable but could be more precise about tweet object structure; no output schema required.

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 already covers both parameters with descriptions and enums; description repeats them without adding new meaning; baseline 3 per high schema coverage.

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?

Clearly states 'Fetch multiple tweets at once (max 10)' with specific verb and resource, and the max limit distinguishes it from sibling tools like get_tweet.

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?

Provides explicit use cases (collecting from list, building feed, comparing) implying when to use, but does not explicitly state when not to use or list alternatives; sibling names help differentiate.

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/zezeron/tweetsave-mcp'

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