Skip to main content
Glama

Go-live status

adgpt_go_live
Read-only

Read-only status of your campaign's live ads: the current go-live, its history, and performance. Starting, renewing or stopping a go-live happens in the web app. Actions: current, history, performance. 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_go_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoParameters for the action (see adgpt_capabilities).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only status'. It adds context beyond the annotations by clarifying that go-live lifecycle changes are not possible here and must be done in the web app, and by disclosing that action parameters are discovered through a separate capabilities call. It does not describe result shape or what happens when an unknown/invalid action-param combination is passed.

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 short sentences, front-loaded with the read-only scope, then the mutation exclusion, then the parameter-discovery pointer. Nothing is redundant and each sentence carries actionable information.

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 no output schema, the description does say what the caller receives (current go-live, history, performance), which covers the return-value burden adequately at this level of detail. The main residual gap is the opaque 'params' object, which is mitigated but not eliminated by the adgpt_capabilities redirect.

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 50% and the 'params' object is free-form with additionalProperties, so the description's enumeration of the three valid actions and the explicit pointer to adgpt_capabilities for per-action parameters genuinely compensates for the schema gap. It still leaves the agent needing a second tool call to learn any params keys, so it is not fully self-sufficient.

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 states a specific verb and resource: read-only status of a campaign's live ads, covering the current go-live, its history, and performance. It also enumerates the three actions (current, history, performance), so an agent can tell this is a status-read tool rather than one of the many campaign/asset siblings. It stops short of differentiating itself from near-neighbours like adgpt_campaigns by name.

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 rules out mutation ('Starting, renewing or stopping a go-live happens in the web app'), which is a genuine when-not statement, and it routes the agent to adgpt_capabilities with the operationId to resolve per-action parameters. What is missing is guidance on which of the three actions to choose for a given need, though the action names are largely self-describing.

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