refresh_accountRenew expired OAuth access tokens for social media accounts to maintain uninterrupted posting and scheduling without re-authentication.
Refresh an account's OAuth access token server-side.
| Name | Required | Description | Default |
|---|---|---|---|
| accountId | Yes |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of disclosing side effectsched. It indicates the operation is server-side and involves OAuth token refresh, but it does not mention whether old tokens are invalidated, whether the account must be connected, what errors may occur, or any irreversible effects.
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 a single, tight, front-loaded sentence with no filler. Every word contributes to naming the action, target, and location of the operation.
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 tool with no annotationsas and no output schema, the description is too minimal. It lacks usage context, side-effect details, and parameter clarification, leaving an agent with insufficient information to invoke it confidently.
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?
The schema has 0% description coverage and the sole required parameter 'accountId' is not described in the tool description. The phrase 'an account's' loosely implies the parameter identifies the account, but the description adds no explicit meaning about format, requirements, or behavior.
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 clearly states the specific action ('Refresh'), the resource ('an account's OAuth access token'), and the context ('server-side'). It is immediately distinguishable from sibling account-management tools like connect_account or disconnect_account and from refresh_analytics.
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 on when to use this tool, what prerequisites must hold (e.g., account must already be connected), or how it differs from alternatives. The description implies a token-refresh scenario but does not explicitly state it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.