Skip to main content
Glama
hellocybernetics

pyX-MCP

search_recent_posts

Search for posts from the past 7 days using X search syntax. Returns up to 100 results with optional expansions and tweet fields.

Instructions

Search for recent posts (past 7 days)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query using X search syntax
expansionsNoList of expansions to request (e.g., author_id)
max_resultsNoMaximum number of posts to return
user_fieldsNoUser fields to request when expansions include author
tweet_fieldsNoAdditional tweet fields to request
Behavior2/5

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

No annotations provided. Description implies a read operation but does not disclose behavioral traits like rate limits, data freshness, or that it returns a list of posts. Minimal transparency.

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?

Single sentence with no fluff. Efficient but could be slightly more detailed without losing conciseness.

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?

With 5 parameters, no output schema, and no annotations, the description provides minimal context (only 7 days constraint). Lacks explanation of search behavior or return value, making it incomplete for an agent.

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% with descriptions for each parameter. Description adds no extra meaning beyond the schema, so baseline score is appropriate.

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

Purpose4/5

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

The description clearly states the verb 'Search', resource 'posts', and a time constraint 'past 7 days'. It is specific but does not differentiate from siblings like get_post or mention search syntax.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives (e.g., get_post for a specific post). The description lacks any 'when' or 'when-not' 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/hellocybernetics/pyX-MCP'

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