Skip to main content
Glama

AdGPT account

adgpt_account

Read your profile, creative-credit balance, and in-flight generations; update your profile. No account yet? Start with register (or login) — the returned session token is adopted automatically and every later call runs as that user. Actions: register, login, me, credits, activeGenerations, updateProfile. 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_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoParameters for the action (see adgpt_capabilities).

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 only say readOnlyHint=false, destructiveHint=false, idempotentHint=false. The description adds genuinely non-obvious behavior: the returned session token is adopted automatically and all later calls run as that user, which changes how an agent sequences everything. It does not say what updateProfile overwrites, whether changes are reversible, or what happens on auth failure, so it is not a 5.

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?

Front-loaded with the read capabilities, then the account-bootstrap prerequisite, then the action list, then the parameter-discovery pointer. Each sentence carries distinct information with no filler. The action list slightly duplicates the enum in the schema, which is minor waste.

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?

A six-action gateway tool with an open-ended params bag and no output schema would be hard to call from the name alone; this description covers what each action touches, the register-first prerequisite, session persistence, and where to find parameter details. What each action returns is still unstated, and there is no output schema to fall back on.

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 an open-ended bag with only 'see adgpt_capabilities' as its description. The tool description compensates by explicitly saying to call adgpt_capabilities with the operationId to learn an action's parameters, which is actionable routing rather than restating the schema. It still names no parameter formats itself, so 4 rather than 5.

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?

Names specific verbs and resources: read profile, creative-credit balance, in-flight generations, update profile, plus register/login. It also enumerates every action, so an agent can match intent to action. It does not explicitly distinguish itself from siblings like adgpt_brands or adgpt_in_action, which keeps it short of a 5.

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?

Gives real sequencing guidance: with no account, start with register or login before anything else. That is a concrete when-to-use instruction most definitions lack. It does not advise when to pick me vs credits vs activeGenerations, or when to reach for a sibling tool instead, so it falls short of a 5.

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