Skip to main content
Glama
Sign In
wechat-official-account

wechat-official-account

by zhuanghaixin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

wechat_get_draft

Read-only

Retrieve a WeChat draft article by its media_id to view or verify content before publishing.

Instructions

根据 media_id 从微信读取草稿内容。

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_id": "<media_id>"
    },
    "name": "wechat_get_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
media_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare read-only and non-destructive behavior. The description adds that this operates on WeChat draft content, but doesn't mention error conditions, return shape, or external dependencies like auth/tokens.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One concise sentence, front-loaded with the action and resource, with no filler or redundancy.

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?

For a simple one-parameter read operation, the description plus annotations are sufficient for basic selection. It could mention return value or failure behavior, but those are not critical for understanding what the tool does.

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

Parameters2/5

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

Schema coverage for the parameter is 0%; the description only repeats 'media_id' without explaining its source, format, or lifecycle. It adds minimal meaning beyond the parameter name.

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

Purpose5/5

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

The description clearly states the action ('read') and the resource ('draft content from WeChat') with an explicit parameter ('media_id'), which distinguishes it from sibling tools like create/validate/check.

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

Usage Guidelines4/5

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

The intended use is obvious: retrieve a draft using its media_id. It doesn't explicitly contrast with alternative tools, but the reading/retrieval context is clear.

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