list_account_articles
List an account's published articles; no API key required
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| account_id | Yes | ||
| include_content | No |
Manto — 馒头新闻
TDQS
B3.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations present, the description carries the full behavioral burden. It adds a useful behavioral detail: no API key is required. However, it does not mention pagination, response shape, rate limits, or what happens with accounts that have no articles.
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?
The description is extremely concise, with no filler words. It front-loads the core purpose and adds one important auth detail in a single short sentence.
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 tool with no annotations, no output schema, and no parameter descriptions, this description is incomplete. It gives the basic purpose but leaves key invocation details, parameter meanings, and behavioral expectations unspecified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/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 for the undocumented parameters. It does not explain limit or include_content, and only weakly implies account_id through the phrase 'an account's.' This is a significant gap for a 3-parameter tool.
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 clearly states a specific verb and resource: listing an account's published articles. It is more specific than sibling tools like get_account or publish, though it does not explicitly differentiate itself from the search or lookup siblings.
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?
The description implies the tool is for retrieving published articles for a given account, but it provides no explicit guidance on when to prefer this tool over alternatives like search or lookup_account. There are no stated exclusions or alternative routing instructions.
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.
TDQS
B3.1/5.0
Disambiguation4/5
Most tools target distinct resources and actions, such as account creation versus lookup versus article listing. Minor overlap exists between get_account (which includes recent content) and list_account_articles, but the descriptions are clear enough to avoid serious misselection.
Naming Consistency4/5
The naming mostly follows a clear verb_noun pattern, e.g., create_account, get_recharge, remove_content, set_promotion. A few tools like publish and search are bare verbs, creating a minor inconsistency, but the overall pattern remains predictable and readable.
Tool Count5/5
Ten tools is well-scoped for a news content management platform covering accounts, publishing, searching, recharges, and promotion. Each tool serves a distinct functional need without unnecessary bloat.
Completeness4/5
The server covers core content lifecycle operations with publish (create/update), remove_content (delete), list_account_articles (read), and search. Minor gaps exist such as no explicit get/delete for accounts or a way to view current promotion settings, but the main workflows are supported.