Skip to main content
Glama
commentkeyword-mcp

commentkeyword-mcp

Official

Get plan usage and account status

get_usage
Read-only

Retrieve your current plan, monthly DM usage, active keywords, connected Instagram account, and any blockers preventing DMs from sending, such as quota limits, failed payments, or reconnection needs.

Instructions

Get the plan, DMs used and included this month, active keywords used and allowed, the connected Instagram account, and anything that stops DMs from going out (Free quota used up, a failed payment, Instagram to reconnect).

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_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish this is a read-only, non-open-world call, and with zero parameters there is no mutation surface to disclose. The description adds real value by naming the specific diagnostic conditions it surfaces (Free quota exhausted, failed payment, Instagram reconnect required) and by implying scoping to the single authenticated account. It still omits any statement about cost, latency, or whether the response is a flat summary or nested structure.

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?

One sentence, front-loaded with the primary payload ('the plan') and building outward to usage counters and then blockers. It is dense but every clause maps to a distinct returned field, so nothing is wasted. A parenthetical list inside a single sentence is slightly harder to scan than a short structured breakdown.

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?

There is no output schema, so the description carries the full burden of describing return content, and it does so concretely field by field, including the failure states that motivate calling it. Combined with read-only annotations and zero parameters, an agent has enough to call this correctly. The only gap is that the shape/ordering of the response is not stated.

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 no parameters, so the baseline is 4. There is nothing for the description to disambiguate, and it correctly spends no words on argument semantics.

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 opens with a specific verb ('Get') and enumerates the exact resources returned: plan, DM usage vs. included quota, active keywords vs. allowance, connected Instagram account, and blocking conditions. An agent can distinguish this from get_stats_overview or get_keyword_stats because this reports account/quota state rather than conversation or keyword metrics. It loses the top score only because it never explicitly names a sibling to contrast against.

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?

Usage is implied rather than stated: the mention of 'anything that stops DMs from going out' signals a diagnostic/health-check purpose, which an agent can reasonably infer. However, there is no explicit 'use this when...' or 'use get_stats_overview instead when...' framing, so the agent must infer the boundary itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.