Skip to main content
Glama

kaedemeta-mcp-server

extract_post_metadata

Extract structured metadata and original high-resolution media URLs from a single X (Twitter), Pixiv, or Danbooru post.

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": {
      "target": "<target>"
    },
    "name": "extract_post_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesPost URL or numeric ID
platformNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a meaningful behavioral detail — that media URLs are the 'original high-resolution' versions rather than thumbnails — but says nothing about authentication needs, rate limits, failure modes on removed posts, or whether media is downloaded versus linked.

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?

A single front-loaded sentence with no filler; the resource and scope land first. It is efficient, though it has room for one short clause on defaults or return shape without becoming bloated.

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?

No output schema exists, so the description must hint at return values, and it does by naming metadata and original-resolution media URLs. For a two-parameter read tool the coverage is adequate; only failure/edge-case behavior is absent.

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?

The schema documents only 'target' ('Post URL or numeric ID') and leaves 'platform' undescribed, so coverage is 50%. The description partially compensates by enumerating the three supported platforms that match the enum values, but it never explains the 'auto' default or how platform detection works when target is a bare numeric ID.

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 gives a specific verb (extract) and a concrete resource (structured metadata plus original high-resolution media URLs) scoped to 'a single X (Twitter), Pixiv, or Danbooru post'. The word 'single' implicitly contrasts with the sibling extract_creator_feed, but no sibling is named, so the differentiation is inferable rather than explicit.

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 only implied: 'from a single post' signals one-post extraction versus a feed, but there is no explicit when-to-use statement, no exclusion of the sibling feed tool, and no note on what happens for private, deleted, or login-gated posts.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources