Skip to main content
Glama

Discover AdGPT capabilities

adgpt_capabilities
Read-only

Search AdGPT operations or describe one in detail (input schema, auth, credit cost, async behavior). Use operationId to describe a specific operation, or query to search by name / domain / path.

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": "adgpt_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSubstring to match against operationId, uri, title, or domain.
operationIdNoReturn the full schema for this single operation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds real value by disclosing the payload of describe mode (input schema, auth requirements, credit cost, async behavior) — credit cost and async semantics are not something the agent could infer from annotations or schema. It stops short of describing what search results look like (fields returned, result limits).

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?

Two sentences, both earning their place, with the two-mode structure stated first and the parameter routing second. Nothing is padded or repeated from the name/title.

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?

For a read-only, optional-parameter discovery tool with no output schema and full schema coverage, the description is nearly sufficient: an agent knows exactly how to invoke each mode and what describe mode yields. The only gap is that search-mode output (result shape, whether it returns operationIds to feed back in) is left implicit.

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 description coverage is 100%, so both parameters are already documented in structured data; the baseline is 3. The description restates the query fields as 'name / domain / path' where the schema says operationId, uri, title, domain, adding only marginal clarification rather than new semantics.

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?

The description names two specific verbs (search, describe) applied to a specific resource (AdGPT operations) and enumerates what the describe mode returns: input schema, auth, credit cost, async behavior. This clearly marks it as the meta-discovery tool, distinguishing it from the sibling operation tools like adgpt_campaigns or adgpt_job that actually perform work.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes between the two modes: operationId for a single operation's detail, query for searching by name/domain/path. That is clear when-to-use-which guidance. It does not, however, say when to reach for this tool at all versus calling a sibling operation directly, which is the main alternative an agent faces.

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