Skip to main content
Glama

Get account

get_account
Read-only

Get the account context for this connection: the organization this token operates on, its subscription plan, limits and current usage, the signed-in user's timezone and digest notification settings, and whether this connection has write access (write_access). It confirms which organization the connection acts on. A null plan means the organization has no subscription. On a read-only connection, new_monitor_url and settings_url are the handoff links for setup and preferences.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
planYes
usageYes
limitsYesPlan limits: monitors counts every monitor in the organization, paused ones included; domains, trademarks, apps and search_ads count the active assets of each type on one monitor. Archived assets free their slot. usage holds the counts these limits apply to.
timezoneYesThe signed-in user's IANA timezone, used for dashboard timestamps and the digest send hour. Null falls back to UTC for the digest.
organizationYes
settings_urlYes
write_accessYesWhether this connection has write access: the mcp:write scope, or an API token with write access. When false, write tools fail until the user reconnects the client and approves the write permission, or switches to an API token with write access.
notificationsYesThe signed-in user's digest settings: daily or off, plus the send hour in the user's timezone. Null when the connection has no user.
new_monitor_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / pricing_url
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "timezone",
      -  "organization",
      -  "plan",
      -  "limits",
      -  "usage",
      -  "notifications",
      -  "write_access",
      -  "new_monitor_url",
      -  "pricing_url",
      -  "settings_url"
      -]New value: +[
      +  "timezone",
      +  "organization",
      +  "plan",
      +  "limits",
      +  "usage",
      +  "notifications",
      +  "write_access",
      +  "new_monitor_url",
      +  "settings_url"
      +]
  2. Changed4 schema fields changed
    • changedOutput schema / properties / limits / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "apps": {
      -        "type": "number"
      -      },
      -      "domains": {
      -        "type": "number"
      -      },
      -      "monitors": {
      -        "type": "number"
      -      },
      -      "trademarks": {
      -        "type": "number"
      -      }
      -    },
      -    "required": [
      -      "monitors",
      -      "domains",
      -      "trademarks",
      -      "apps"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "apps": {
      +        "type": "number"
      +      },
      +      "domains": {
      +        "type": "number"
      +      },
      +      "monitors": {
      +        "type": "number"
      +      },
      +      "search_ads": {
      +        "type": "number"
      +      },
      +      "trademarks": {
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "monitors",
      +      "domains",
      +      "trademarks",
      +      "apps",
      +      "search_ads"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / limits / description
      Previous value: -"Plan limits: monitors counts every monitor in the organization, paused ones included; domains, trademarks and apps count the active assets of each type on one monitor. Archived assets free their slot. usage holds the counts these limits apply to."New value: +"Plan limits: monitors counts every monitor in the organization, paused ones included; domains, trademarks, apps and search_ads count the active assets of each type on one monitor. Archived assets free their slot. usage holds the counts these limits apply to."
    • addedOutput schema / properties / usage / properties / by_monitor / items / properties / search_ads
      Added value: +{
      +  "type": "number"
      +}
    • changedOutput schema / properties / usage / properties / by_monitor / items / required
      Previous value: -[
      -  "monitor_id",
      -  "name",
      -  "status",
      -  "domains",
      -  "trademarks",
      -  "apps"
      -]New value: +[
      +  "monitor_id",
      +  "name",
      +  "status",
      +  "domains",
      +  "trademarks",
      +  "apps",
      +  "search_ads"
      +]
  3. Changed3 schema fields changed
    • addedOutput schema / properties / timezone
      Added value: +{
      +  "description": "The signed-in user's IANA timezone, used for dashboard timestamps and the digest send hour. Null falls back to UTC for the digest.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • removedOutput schema / properties / user
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "additionalProperties": false,
      -      "properties": {
      -        "email": {
      -          "type": "string"
      -        },
      -        "name": {
      -          "type": "string"
      -        },
      -        "timezone": {
      -          "description": "The user's IANA timezone, used for dashboard timestamps and the digest send hour. Null falls back to UTC for the digest.",
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        }
      -      },
      -      "required": [
      -        "name",
      -        "email",
      -        "timezone"
      -      ],
      -      "type": "object"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ]
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "user",
      -  "organization",
      -  "plan",
      -  "limits",
      -  "usage",
      -  "notifications",
      -  "write_access",
      -  "new_monitor_url",
      -  "pricing_url",
      -  "settings_url"
      -]New value: +[
      +  "timezone",
      +  "organization",
      +  "plan",
      +  "limits",
      +  "usage",
      +  "notifications",
      +  "write_access",
      +  "new_monitor_url",
      +  "pricing_url",
      +  "settings_url"
      +]
  4. Changed1 schema field changed
    • changedOutput schema / properties / write_access / description
      Previous value: -"Whether this connection has write access: the mcp:write scope, or an agent token with write access. When false, write tools fail until the user reconnects the client and approves the write permission, or switches to an agent token with write access."New value: +"Whether this connection has write access: the mcp:write scope, or an API token with write access. When false, write tools fail until the user reconnects the client and approves the write permission, or switches to an API token with write access."
  5. Changed1 schema field changed
    • changedOutput schema / properties / write_access / description
      Previous value: -"Whether this connection holds the mcp:write scope. When false, write tools fail until the user reconnects the client and approves the write permission."New value: +"Whether this connection has write access: the mcp:write scope, or an agent token with write access. When false, write tools fail until the user reconnects the client and approves the write permission, or switches to an agent token with write access."
  6. Changed5 schema fields changed
    • removedOutput schema / properties / billing_url
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / organization / properties / id
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / properties / organization / required
      Previous value: -[
      -  "id",
      -  "name"
      -]New value: +[
      +  "name"
      +]
    • addedOutput schema / properties / pricing_url
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "user",
      -  "organization",
      -  "plan",
      -  "limits",
      -  "usage",
      -  "notifications",
      -  "write_access",
      -  "new_monitor_url",
      -  "billing_url",
      -  "settings_url"
      -]New value: +[
      +  "user",
      +  "organization",
      +  "plan",
      +  "limits",
      +  "usage",
      +  "notifications",
      +  "write_access",
      +  "new_monitor_url",
      +  "pricing_url",
      +  "settings_url"
      +]
  7. Changed3 schema fields changed
    • addedOutput schema / properties / limits / description
      Added value: +"Plan limits: monitors counts every monitor in the organization, paused ones included; domains, trademarks and apps count the active assets of each type on one monitor. Archived assets free their slot. usage holds the counts these limits apply to."
    • addedOutput schema / properties / usage
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "active_monitors": {
      +      "description": "Active monitors; resuming a paused monitor needs this below limits.monitors.",
      +      "type": "number"
      +    },
      +    "by_monitor": {
      +      "description": "Active assets of each type per monitor; add_asset needs the count for its type below the matching limit.",
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "apps": {
      +            "type": "number"
      +          },
      +          "domains": {
      +            "type": "number"
      +          },
      +          "monitor_id": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "status": {
      +            "enum": [
      +              "active",
      +              "paused"
      +            ],
      +            "type": "string"
      +          },
      +          "trademarks": {
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "monitor_id",
      +          "name",
      +          "status",
      +          "domains",
      +          "trademarks",
      +          "apps"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "monitors": {
      +      "description": "All monitors, paused ones included; create_monitor needs this below limits.monitors.",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "monitors",
      +    "active_monitors",
      +    "by_monitor"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "user",
      -  "organization",
      -  "plan",
      -  "limits",
      -  "notifications",
      -  "write_access",
      -  "new_monitor_url",
      -  "billing_url",
      -  "settings_url"
      -]New value: +[
      +  "user",
      +  "organization",
      +  "plan",
      +  "limits",
      +  "usage",
      +  "notifications",
      +  "write_access",
      +  "new_monitor_url",
      +  "billing_url",
      +  "settings_url"
      +]
  8. Changed1 schema field changed
    • changedOutput schema / properties / write_access / description
      Previous value: -"Whether this connection holds the mcp:write scope. When false, write tools fail; reconnect with the write permission approved."New value: +"Whether this connection holds the mcp:write scope. When false, write tools fail until the user reconnects the client and approves the write permission."
  9. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), so the description is free to add semantics it alone can supply: a null plan means no subscription, write_access reports whether the connection can write, and on read-only connections new_monitor_url/settings_url are the handoff links. It stops short of noting freshness/caching or any rate-limit behavior, which keeps it from 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?

Three sentences, front-loaded with the returned contents, then the scoping statement, then the edge cases (null plan, read-only handoff). The field enumeration is dense but each item is load-bearing; the only mild redundancy is restating the org-scoping that the opening clause already implies.

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?

An output schema exists, so return values need not be spelled out, yet the description still names the key fields and interprets the two ambiguous ones (null plan, write_access) plus the read-only URL semantics. That is sufficient for a zero-parameter, read-only context tool; only minor operational details like data freshness are absent.

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?

The tool takes zero parameters, so the schema imposes nothing to explain and the baseline of 4 applies. The description spends its words on the response instead, which is the right allocation here.

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 opens with a specific verb+resource ('Get the account context for this connection') and then enumerates the exact payload: organization, subscription plan, limits/usage, timezone, digest settings, and write_access. That is enough for an agent to distinguish it from the match/monitor/takedown siblings without opening any schema.

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?

Usage is implied rather than stated: the agent can infer it should call this to learn which organization a token acts on, whether the connection can write, and where to send a user for setup on a read-only connection. There is no explicit when-to-use/when-not framing or named alternative, though the sibling set contains no other account-scoped tool to route against.

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