Skip to main content
Glama

x_api_get_posts_quoted_posts

Retrieve posts that quote a specified post ID, including pagination and exclusion filtering.

Instructions

Get Quoted Posts. Use when: Get Quoted Posts. 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; OAuth 1a user token 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: id (path, unknown, required); max_results (query, integer); pagination_token (query, unknown); exclude (query, array). 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_get_posts_quoted_posts","arguments":{"scopeTenantId":"default","scopeUserId":"default","id":""}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
excludeNo
max_resultsNo
scopeUserIdNo
credentialKeyNo
scopeTenantIdNo
scopeAccountIdNo
authorizationKeyNo
pagination_tokenNo
preferredAuthTypeNo
Behavior4/5

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

With no annotations, the description carries the burden, and it discloses read-only risk, auth token/scopes, environment-selection behavior, common failure conditions, and a warning about sensitive response data. It does not describe the actual content/returned fields, but the provided transparency is substantial.

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 labeled sections make the content scannable, but there is redundancy ('Use when: Get Quoted Posts' restates the title; read-only appears twice) and some boilerplate failure conditions that may not apply. Overall it's organized but not tight.

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?

For a 10-parameter tool with no output schema, the description covers auth, environment selection, expected response envelope, and an example, but it never specifies the shape or meaning of the quoted-posts data returned, and several parameters remain unexplained. It's adequate for invocation but incomplete for full understanding.

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 0%, so the description must compensate. It lists parameter formats/constraints for id, max_results, pagination_token, and exclude, and explains scopeTenantId/scopeUserId/scopeAccountId/credentialKey in prose, but omits semantics for authorizationKey, preferredAuthType, and doesn't explain exclude values or pagination token usage.

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 opens with 'Get Quoted Posts,' a clear verb+resource pairing that identifies the operation. However, it doesn't differentiate from sibling tools like x_api_get_posts_reposts or x_api_get_posts_reposted_by, so it falls short of full specificity.

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?

The 'Use when' section merely restates the tool name ('Get Quoted Posts') and offers no concrete triggers. 'Do not use when' gives generic exploratory guidance and fails to name alternative API tools; recommended prerequisite/follow-up tools are listed but not as decision criteria.

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