Skip to main content
Glama

Lead sheet sync status

lead_sheet_sync_status
Read-onlyIdempotent

Lists the Google Sheets leads are sent to in the workspace's accounts (syncId, the campaign, ad set or ad, the sheet's link, leads sent, the last error) and the connected person's Google sign-ins, with the sign-in link when none can create a sheet. A sheet opens for whoever its owner shared it with in Google.

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": {
      "input": "<input>"
    },
    "name": "lead_sheet_sync_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the sign-in link surfaced when no one can create a sheet, and the sharing caveat that a sheet opens only for whoever its owner shared it with in Google. It still says nothing about result size, pagination, or whether unsynced/failed syncs are included.

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?

Two sentences, front-loaded with the primary result set and followed by the secondary sign-in information. The long parenthetical field list makes the first sentence heavy, but no sentence is filler.

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?

There is no output schema, so the description correctly takes on the job of enumerating returned fields, and it covers both halves of the response (sheet destinations and Google sign-ins). The main remaining gap is scale/pagination behavior, which matters for a listing tool but is a minor omission overall.

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 coverage is 75%, with accountIds, userStatement and idempotencyKey already documented in the schema; accountId is undocumented in both places. The description only hints at scoping with 'in the workspace's accounts' and adds no detail about account selection or why idempotencyKey matters for a read-only listing.

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 names a specific verb ('Lists') and a specific resource (the Google Sheets that leads are sent to, plus connected Google sign-ins), and enumerates the returned fields (syncId, campaign/ad set/ad, sheet link, leads sent, last error). That is far more concrete than the title, though it does not explicitly contrast itself with siblings such as leads_read or integrations_status.

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: an agent can infer this is the tool to check where leads are being delivered and whether delivery failed ('the last error'). There is no explicit when-to-use/when-not guidance and no named alternative for related questions about leads themselves or integration health.

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.