Skip to main content
Glama

BRAINIAC Ecommerce Seller Profitability

Check listing keyword coverage and length limits

ecommerce-profitability_listing-keyword-coverage
Read-onlyIdempotent

Token-match caller keywords against title, bullets, description and backend terms, including simple plurals, and check caller-supplied title and backend length limits. Price $0.02 USDC. POST /api/v1/ecommerce-profitability/listing-keyword-coverage. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "keywords": "<keywords>",
      "limits": "<limits>"
    },
    "name": "ecommerce-profitability_listing-keyword-coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYestitle, string, length 0 to 2000. Required.
limitsYeslimits, object. Required.
bulletsNobullets, array. Required.
keywordsYeskeywords, array. Required.
descriptionNodescription, string, length 0 to 20000. Required.
backendTermsNobackendTerms, string, length 0 to 2000. Required.

Output Schema

NameRequiredDescriptionDefault
lengthsNolengths. Object.
sourcesNosources. Array.
coverageNocoverage. Number.
keywordsNokeywords. Array.
overLimitNooverLimit. Array.
limitationsNolimitations. Array.
duplicatesInBackendNoduplicatesInBackend. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: a $0.02 USDC cost, a POST transport, and the critical fact that an unpaid call returns x402 payment terms without executing. That unpaid-no-op clause is exactly the kind of detail an agent needs before invoking. It stops short of describing matching edge cases (case sensitivity, multi-word phrases, stemming beyond plurals).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: what it computes first, then cost/endpoint, then the payment-gate caveat. Every sentence carries information the agent cannot get from the schema or annotations, and nothing is padded.

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?

With an output schema present and full annotation coverage, the description needs only to explain inputs, cost, and the payment behavior, and it does all three. The remaining gap is the matching semantics — stemming, case handling, phrase matching — which directly affect result interpretation for a keyword-coverage tool.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by mapping the searched fields (title, bullets, description, backend terms) and clarifying that limits means title character limits and backend byte limits. It also discloses that matching includes simple plurals, which the schema does not. Ambiguity remains about how limits objects are interpreted against the input fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific operation ('token-match caller keywords against title, bullets, description and backend terms') plus a second distinct check on length limits. This is unmistakably different from every sibling, which are pricing/economics tools, so an agent can route on the description alone.

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 when-to-use or when-not-to-use guidance and no named alternative. The agent must infer from the verb that this is a listing SEO/keyword audit rather than a pricing analysis; nothing tells it what problem this solves or in what sequence to call it.

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