Skip to main content
Glama
Sign In

Agency Autopilot

by com.jiyumarketing.mcp
OverviewDiscussionsAdmin

Client: rename, website, report contact and language

update_client
DestructiveIdempotent

Edit a client the way the dashboard's client editor does: rename it, set its website, or set who gets its weekly report (contact name and email) and the report's language. Linking or unlinking accounts has its own tools (link_account, unlink_account). Call without confirm to preview; changes only this agency's records. Removing a client is done on the dashboard (account_links).

Input Schema

NameRequiredDescriptionDefault
clientYesClient name from list_clients
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.
rename_toNo
website_urlNoEmpty string clears it
not_lead_eventsNoGA4 key events that are NOT leads for this client (e.g. ["sign_up"] when the property also records another product's sign-ups). They stay key events in GA4; Autopilot's lead counts leave them out. [] clears it.
report_languageNo
report_lead_namesNoShow each lead's name in this client's weekly report (default true: they're the client's own leads; false shows only the town and what they asked for)
report_contact_nameNo
report_contact_emailNoWho receives the weekly Autopilot report; empty string clears it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / report_lead_names
      Added value: +{
+  "description": "Show each lead's name in this client's weekly report (default true: they're the client's own leads; false shows only the town and what they asked for)",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / not_lead_events
      Added value: +{
+  "description": "GA4 key events that are NOT leads for this client (e.g. [\"sign_up\"] when the property also records another product's sign-ups). They stay key events in GA4; Autopilot's lead counts leave them out. [] clears it.",
+  "items": {
+    "maxLength": 40,
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false, so the description's most valuable addition is the dry-run/confirm protocol and the blast-radius note 'changes only this agency's records'. It does not describe what the preview output looks like or whether clearing a field is irreversible, leaving some behavioral gaps.

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 dense sentences, front-loaded with the core action before the sibling routing and preview note. Slightly overpacked parentheticals ('(account_links)') but every sentence contributes routing or behavioral information.

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 9-parameter destructive mutation with no output schema, the description covers scope, preview semantics, and sibling boundaries, and the confirm parameter's schema text explains the preview return. The main omission is the lead-exclusion / lead-name reporting options, which are only discoverable in the schema.

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 67% and the description compensates for the undocumented parameters by naming the fields it accepts (rename, website, report contact name/email, report language), which directly maps to the schema's undescribed properties rename_to, report_language and report_contact_name. It says nothing about not_lead_events or report_lead_names, but those carry solid schema descriptions.

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?

States a specific verb and resource ('Edit a client') and enumerates the editable facets: rename, website, weekly-report contact name/email, and report language. It explicitly carves out sibling scope by naming link_account and unlink_account for account linking and account_links/dashboard for removal, so an agent can distinguish it without opening a schema.

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?

Gives explicit when-to-use routing ('Linking or unlinking accounts has its own tools (link_account, unlink_account)') and an explicit when-not ('Removing a client is done on the dashboard (account_links)'). It also states the preview-first protocol ('Call without confirm to preview'), which dictates the correct invocation sequence.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agency Autopilot toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources