Skip to main content
Glama

douyin-xiaohongshu-rednote-social-scraper-mcp

get_account_status

Read-only

Inspect paid_usd, bonus_usd, rate limit, and active sub-key caps.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_account_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description contributes the concrete set of values surfaced (paid/bonus balance, rate limit, sub-key caps), which is real added context, but it says nothing about authentication requirements, units, or freshness of the counters. With annotations carrying safety, a 3 is appropriate.

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 short imperative sentence with no filler, and the highest-value items lead. It is telegraphic to the point of being slightly opaque — 'inspect' followed by bare field names reads like a payload listing rather than an explanation of what the tool returns.

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 no-parameter, read-only tool with no output schema, the description covers the essential return content (balances, rate limit, sub-key caps), which is what an agent needs to decide to call it. Missing only framing details such as units or whether the values are per-account versus per-key.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The field names mentioned describe outputs rather than inputs, which is harmless but does not strengthen parameter meaning.

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 verb 'Inspect' plus the enumerated fields (paid_usd, bonus_usd, rate limit, active sub-key caps) makes clear this reads account-level billing and quota state. That is distinct from the endpoint-oriented siblings (get_endpoint_schema, call_endpoint, search_endpoints), though the description never explicitly frames the tool as 'account status' to reinforce the separation.

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

Usage Guidelines2/5

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

There is no stated condition for calling it (e.g., 'call before running batch jobs to check remaining quota') and no mention of when not to call it or which sibling to prefer. The only usage signal is implicit in the field list itself.

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