Skip to main content
Glama

Brands

adgpt_brands
Destructive

Manage brands: list, get, create, update, delete, and auto-fetch details from a URL (costs 5 credits). Actions: list, get, create, update, delete, fetchDetails. Call adgpt_capabilities with the operationId to see an action's parameters.

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": {
      "action": "<action>"
    },
    "name": "adgpt_brands"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoParameters for the action (see adgpt_capabilities).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is supplied. The description adds a concrete cost signal (fetchDetails costs 5 credits), but it does not say which of the six actions are the destructive ones (delete vs list) nor what delete actually removes, which is the key extra context a multiplexed tool could provide.

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?

Two short sentences, front-loaded with the resource and action list, with no filler. The explicit action enumeration is slightly redundant with the enum but aids scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a multiplexed tool with a generic params bag and no output schema, the description covers the action set and defers parameter detail to a companion tool, which is reasonable. It still omits which actions mutate or destroy data and what identifiers each action expects, leaving the agent dependent on a second call to proceed safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, and the free-form "params" object is essentially undocumented in the schema. The description partially compensates by naming the action values and pointing to adgpt_capabilities for per-action parameters, but it provides no actual parameter meaning itself.

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 and resource ("Manage brands") and enumerates all six actions, so an agent knows exactly what domain this tool covers versus siblings like adgpt_campaigns or adgpt_catalog. The enumeration matches the action enum, making the intent unambiguous.

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?

It tells the agent how to discover per-action parameters ("Call adgpt_capabilities with the operationId"), which is a useful routing hint, and flags the cost of fetchDetails. However, it gives no guidance on when to choose this tool over siblings or when an action is inappropriate, leaving usage context largely implied.

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