Skip to main content
Glama

Account: dashboard links for billing, credits, deleting and disconnecting

account_links
Read-onlyIdempotent

Dashboard links for what the assistant does not do itself (money, secrets and deletion): billing (plan, seats, payment), prospect credits (balance, packs, the unlimited plan), white label domains and email senders, team invites, assistants, privacy and deleting data, removing a client, disconnecting or removing a connection, the client portal. Also the prospect credits balance. Reconnecting a platform: its connect tool (connect_google, connect_meta, connect_business_profile, connect_crm, connect_wordpress). Never takes payment; the person pays on the page. Read-only.

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_links"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: it does not execute payment itself, and deletion/secrets are handled on the linked page rather than by the tool. That is meaningful context an agent would otherwise not have.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core framing is front-loaded, but the body is a comma-spliced laundry list, and 'Also the prospect credits balance' redundantly restates an item already named earlier. The content is useful but could be grouped and trimmed considerably.

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 and no parameters, the description carries the full burden of explaining what the agent gets back, and naming the link categories does that adequately. A short note on return shape (list of labeled URLs) would close the remaining gap.

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 baseline is 4; the schema has nothing to document and the description introduces no parameter concepts. There is no gap to compensate for.

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 identifies a specific resource — dashboard links for actions the assistant does not perform itself — and enumerates the covered domains (billing, credits, deletion, connections, portal). It distinguishes itself from mutation siblings by framing these as outbound links rather than operations. However, it never plainly says it returns URLs, and the sprawling list dilutes the core statement.

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 reconnection requests to the connect_* siblings by name (connect_google, connect_meta, etc.), which is a clear use-the-other-tool rule. It also sets a boundary with 'Never takes payment; the person pays on the page.' It lacks a clean positive statement of when to reach for this tool over, say, client_access_link or list_connected_accounts.

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.