get_commentRetrieves a single scheduled comment by its unique ID, providing the exact details needed to review or manage your scheduled social media content.
Fetch one scheduled comment.
| Name | Required | Description | Default |
|---|---|---|---|
| commentId | Yes |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a read operation via 'Fetch' but does not mention response format, error behavior, authorization requirements, or whether any side effects occur.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is four words, front-loaded, and contains no filler. Every word earns its place and the core purpose is immediately visible.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter getter, the basic call contract is present and usable. However, with no output schema and no annotations, the absence of return-value and behavioral information leaves gaps that a fuller definition could close.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description adds no detail about the commentId parameter beyond what its name implies. This is a slight gap because the tool description should compensate for the undocumented schema, even for a single obvious parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('Fetch') and resource ('one scheduled comment'), and the singular scope clearly distinguishes it from list_comments and from object types like get_post or get_organization. The purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given for when to use this tool instead of alternatives such as list_comments or get_post. The agent must infer that this is the single-comment-by-ID lookup tool from the description alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.