Skip to main content
Glama
kaedemeta-mcp-server

kaedemeta-mcp-server

extract_creator_feed

Batch extract original media URLs and structured metadata from a creator’s X or Pixiv profile, or Danbooru tags, to collect downloadable posts and details in one pass.

Instructions

Batch extract original media URLs and metadata from a creator's profile/timeline (@username for X, users/ID for Pixiv) or Danbooru tags.

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_creator_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
targetYes@username, creator profile URL, or tag
platformNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations and no output schema, so the description carries the full disclosure burden. 'Batch extract' hints at bulk volume, but nothing is said about rate limits, authentication needs, whether pagination is required to exhaust a feed, what 'original' excludes (e.g., reposts), or how partial failures are handled across a batch.

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 dense sentence with the core action front-loaded and the platform-specific target formats parenthetically grouped. No filler, though the parenthetical platform mapping makes the sentence long enough to be slightly harder to parse at a glance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter, multi-platform extraction tool with no annotations and no output schema, the definition omits return shape, pagination behavior, platform 'auto' resolution, and any safety or rate-limit context. It identifies the sources well but leaves too much of the calling contract unspecified.

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 only 25%, so the schema alone does not document page, limit, or platform. The description does add real meaning for target (mapping input formats to platforms) and implies platform inference, but leaves page, limit defaults, and the 'auto' enum value unexplained.

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 names a specific verb and resource — 'batch extract original media URLs and metadata' — and scopes it to a creator profile/timeline or Danbooru tags, with per-platform target formats. It implicitly separates itself from extract_post_metadata by operating on a creator feed rather than an individual post, but it never names that sibling explicitly.

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 target-type examples (@username for X, users/ID for Pixiv, tags for Danbooru), which tells the agent what input shape selects which source. There is no explicit when-to-use versus extract_post_metadata, no statement of when this tool is the wrong choice, and no prerequisite or failure conditions.

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

Deploy Server

Other Tools