Skip to main content
Glama

Account Management

account
Destructive

View or update your account (authenticate with your API token sk_...; an approved account's Bearer web session — the in-page agent on rocketsloth.ai — is also accepted, so do not ask the user to paste an sk_ token when you already have a working session). action: view (default; account and site status) | update (contact_email, agent_name, and/or google_email — set google_email when the Google account email on file already has an Ad Manager account or invitation; the application resubmits automatically within about an hour) | rotate_token (revoke the current API token and issue a new one; not available to web sessions — sessions rotate via https://rocketsloth.ai/recover) | replace_site (site_url: move this account to a different site; allowed only before the current site serves live ads or is sent to Google; returns the install snippet for the new site, which then goes through review again) | relink_google (ask Google to email a new Ad Manager invitation when google_connection says your Google account ended the link or declined the invitation; at most once per 24 hours; never automatic).

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

Input Schema

NameRequiredDescriptionDefault
tokenNoYour API token (sk_...). May instead be sent as an Authorization: Bearer header.
actionNoOne of: view (default), update, rotate_token, replace_site, relink_google. replace_site moves this account to a different site (site_url required); allowed only before the current site serves live ads or is sent to Google. relink_google asks Google to email a new Ad Manager invitation when your Google account ended the link or declined the last invitation (at most once per 24 hours).
site_urlNoFor action=replace_site: the new site, as a root domain URL (e.g. https://example.com).
agent_nameNoFor action=update: a new agent name.
google_emailNoFor action=update: the Google account email your Ad Manager invitation goes to. Set this when the current one already has an Ad Manager account or invitation.
contact_emailNoFor action=update: a new contact email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"One of: view (default), update, rotate_token."New value: +"One of: view (default), update, rotate_token, replace_site, relink_google. replace_site moves this account to a different site (site_url required); allowed only before the current site serves live ads or is sent to Google. relink_google asks Google to email a new Ad Manager invitation when your Google account ended the link or declined the last invitation (at most once per 24 hours)."
    • addedInput schema / properties / site_url
      Added value: +{
      +  "description": "For action=replace_site: the new site, as a root domain URL (e.g. https://example.com).",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / google_email
      Added value: +{
      +  "description": "For action=update: the Google account email your Ad Manager invitation goes to. Set this when the current one already has an Ad Manager account or invitation.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/openWorldHint annotations by disclosing the actual damage profile: rotate_token revokes the current token, replace_site resets the site and forces a new review cycle, relink_google is rate-limited to once per 24 hours and is never automatic, and update resubmits automatically within about an hour. It also names the auth paths (sk_ token vs. approved web session) and the web-session exclusion for rotate_token.

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?

The core purpose is front-loaded and every clause carries operational detail, but the single dense sentence with nested em-dash parentheticals is hard to scan and repeats the action semantics that the schema already documents.

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 destructive, multi-action, zero-required-parameter tool with no output schema, it covers preconditions, rate limits, and return behavior for replace_site's install snippet. The only gap is what rotate_token returns or how to handle the newly issued token, and what fields 'view' reports.

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 the schema already explains token, action, site_url, agent_name, google_email and contact_email. The description largely restates these (site_url root domain, google_email conditional), adding only the cross-reference to google_connection state, so baseline 3 applies.

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?

Opens with a concrete verb+resource ('View or update your account') and then enumerates all five actions with their distinct effects, so an agent can tell 'view'/'update' apart from 'rotate_token'/'replace_site'/'relink_google' without opening the schema. It also distinguishes itself from the 'recover' sibling by naming the recover URL for web-session token rotation.

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

Usage Guidelines5/5

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

Explicit routing rules throughout: do not ask for an sk_ token when a Bearer web session already works, set google_email when the Google account already has an Ad Manager account or invitation, use replace_site only before the site serves live ads or is sent to Google, and use relink_google only when google_connection shows the link ended or was declined. Both when-to-use and when-not conditions are stated.

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