Skip to main content
Glama
X Use

X Use

by felixlark

Read X media metadata

x_media
Read-onlyIdempotent

Read media metadata by media key through X API v2, returning structured JSON or classified errors without fabricating data. Read-only.

Instructions

Read media metadata by media key. The direct endpoint may be forbidden when the developer App is not enrolled in a Project; the error is returned without fabricating data. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "media_key": "<media_key>"
    },
    "name": "x_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
media_keyYesX media key in the form <type>_<id>.
media_fieldsNoMapped to media.fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds real value beyond them by disclosing a specific failure mode (App not enrolled in a Project causes a forbidden error) and by promising that the error is returned without fabricated data. That non-fabrication guarantee is unusually useful for an agent deciding whether to trust the result.

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?

Three short clauses, front-loaded with the purpose before the error caveat. The trailing "Read-only." largely duplicates the readOnlyHint annotation and is the one sentence that does not earn its place.

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?

This is a simple two-parameter read tool, and the description covers purpose, one important failure mode, and the no-fabrication behavior. There is no output schema, so the description would ideally hint at the shape of returned media metadata, but the core call path is fully specified.

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%, so both params (media_key with its <type>_<id> format, and media_fields mapped to media.fields) are already documented in the schema. The description only repeats "by media key" and adds nothing about media_fields or field selection, so the baseline 3 applies.

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?

States a specific verb and resource: "Read media metadata by media key." This is clearly distinguishable from the sibling tools, which are all post, search, status, thread, and user oriented rather than media oriented. It does not explicitly name a sibling to route against, which keeps it short of a 5.

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?

Usage is implied by the input (a media key), and the description supplies one prerequisite-like signal: the direct endpoint may be forbidden when the developer App is not enrolled in a Project. It never says when to prefer this over the other X tools or what to do after such an error, so the guidance stays minimal.

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