get_my_ad_usageFor a connected AdCreator (Shopify) merchant: how many ad creatives and videos you have used this month, your plan limits, what is left, and your all-time creatives. Requires your AdCreator connection token (add this server with an Authorization: Bearer adcmcp_… header). If not connected, it explains how to connect. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint. The description adds meaningful behavior beyond that: it requires a specific Authorization Bearer adcmcp_… header, explains that an unconnected merchant will receive connection instructions, and reaffirms the operation is read-only. No contradiction with annotations.
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 compact and front-loaded with the core purpose, then covers the auth prerequisite and fallback behavior in a few tight sentences. Every sentence adds useful information without redundancy.
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 zero-parameter, read-only usage query, the description is nearly complete: it states the inputs it needs (connection token), the outputs it provides (creatives used, limits, remaining, all-time), and behavior when not connected. It does not specify the exact response format, but no output schema exists and the described data points are sufficient for tool selection.
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 tool has zero parameters and the schema coverage is 100%, so there is no parameter ambiguity for the description to resolve. The auth token mentioned in the description is a server configuration requirement, not an input parameter, and it is clearly described.
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 uses a specific verb and resource: it reports AdCreator usage for a connected Shopify merchant. It enumerates exactly what is returned — monthly ad creatives and videos, plan limits, what is left, and all-time creatives — which makes the tool's purpose unambiguous and distinguishable from the sibling tools.
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?
It clearly states the intended context: a connected AdCreator merchant wanting usage information. It also gives the key prerequisite, the AdCreator connection token, and notes what happens when not connected. It does not explicitly compare against the sibling get_my_plan tool, but the context is clear enough for correct selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The three tools have clearly separate purposes: one generates ad headlines, one reports usage, and one reports plan details. The two account-related tools could theoretically be confused, but their descriptions make the distinction between usage limits and plan details clear.
Tool names follow a consistent verb_noun pattern with no mixed conventions. generate_ad_headlines, get_my_ad_usage, and get_my_plan are all predictable and readable.
Three tools is a reasonable, focused set for a niche server that handles headline generation plus basic account checks. It is slightly minimal but not too thin for the stated purpose.
The core advertised functionality is covered: headline generation, usage monitoring, and plan information. There are minor gaps such as no explicit creative-generation or account-management tools, but these fall outside the primary headline-generation scope.