Skip to main content
Glama

x_api_search_news

Search X for news matching a query, with optional limits on number and age of results. Returns news items from the X API.

Instructions

Search News. Use when: Search News. Do not use when: a more specific auth/configuration tool is required before the API call or you are only exploring; prefer x_schema_discovery or x_query_suggestion first. Risk: read-only. Required permissions and prerequisites: bearer token; OAuth 2 user token with scopes tweet.read, users.read Environment-selection behavior: scopeTenantId plus exactly one of scopeUserId or scopeAccountId choose the Vault/Postgres tenant principal used for auth resolution. credentialKey selects a non-default stored credential profile when present. Parameter formats and constraints: query (query, string, required); max_results (query, integer); max_age_hours (query, integer). Expected response shape: { ok, status, data: { method, path, url, status, contentType, authType, data } } Common failure conditions: missing scoped credentials in Vault, missing required API parameters, X API auth failures, rate limits, or unsupported multipart/body shape. Recommended prerequisite and follow-up tools: x_connection_info, x_schema_discovery, x_auth_get_scope_credentials, x_api_request. Safety warnings: This is read-only, but responses can still include sensitive account data depending on granted scopes. Example: {"name":"x_api_search_news","arguments":{"scopeTenantId":"default","scopeUserId":"default"}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
max_resultsNo
scopeUserIdNo
credentialKeyNo
max_age_hoursNo
scopeTenantIdNo
scopeAccountIdNo
authorizationKeyNo
preferredAuthTypeNo
Behavior5/5

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

With no annotations, the description fully discloses read-only risk, required OAuth scopes, environment-selection behavior, common failure conditions, and a safety warning about sensitive account data. This goes well beyond minimal expectations.

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 well-structured with labeled sections but is verbose, repeating 'Search News' and 'read-only' multiple times. Some information (parameter types) duplicates the input schema, though the labels aid scanning.

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?

It covers response shape, failure conditions, prerequisites, and gives an example, which is useful given no output schema. However, it does not explain the actual content of the returned `data` (e.g., a list of news articles) or pagination behavior.

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

Parameters4/5

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

The description explains the meaning of scopeTenantId, scopeUserId/scopeAccountId, and credentialKey in the environment-selection behavior, and lists query, max_results, and max_age_hours with types. However, it omits authorizationKey and preferredAuthType, and does not clarify query syntax or valid ranges.

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

Purpose3/5

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

The description opens with 'Search News' and repeats 'Use when: Search News', which is tautological. It does not define what 'News' means in the X API context or differentiate this from sibling tools like x_api_get_news or x_api_search_posts_recent.

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

Usage Guidelines3/5

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

It provides explicit 'Do not use when' guidance (prefer x_schema_discovery or x_query_suggestion when exploring) and lists recommended prerequisite tools, but the core 'Use when' is circular and there is no comparison to other search tools.

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/LesterAJohn/X-mcp'

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