Skip to main content
Glama

Pagetool

Save the client record for a site

set_client_record
Idempotent

Saves who a site is for and where things stand: business name, contact name/email/phone, the source pages its facts came from, status (prospect, pitched, managed, declined, transferred_out) and notes. Only the fields you pass change; null clears one. list_sites shows each site's record.

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

Input Schema

NameRequiredDescriptionDefault
notesNoFree-text notes (max 5000 chars). Null clears them.
statusNoWhere the relationship stands.
site_keyNoThe site the record is about. Defaults to the caller's current draft site when omitted.
draft_tokenNoThe draft token returned by draft_create, if you are working on an anonymous draft. Only needed when your client cannot send the x-pagetool-draft-token header.
source_urlsNoThe business's own pages the site's facts came from (http/https, max 20). Replaces the stored list.
contact_nameNoThe person to talk to at the business. Null clears it.
business_nameNoThe client business name. Null clears it.
contact_emailNoTheir email. Null clears it.
contact_phoneNoTheir phone. Null clears it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, and the description adds genuinely non-structured behavior: field-level patch semantics and the fact that null is the clear signal. It does not mention permission requirements, whether status transitions are constrained, or the cost of overwriting a stored record, which would round out a mutation tool.

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

Conciseness5/5

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

Three tight sentences: what is written, how updates behave, where to read it. No filler, and the field inventory is front-loaded so an agent knows the payload shape immediately.

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, all-optional mutation tool with no output schema and full schema coverage, the description covers purpose, content and update semantics adequately. It leaves the draft_token / anonymous-draft path and the site_key default entirely to the schema, which is acceptable but means the description alone would not let an agent reason about the draft workflow.

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 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema does not: partial-update semantics and null-as-clear apply uniformly across every optional field. It also restates the status vocabulary to frame the field as the relationship stage; it omits draft_token and site_key defaults, which the schema already covers.

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 ('Saves ... the client record for a site') and enumerates the exact contents: business name, contact details, source pages, status and notes. The closing pointer to list_sites for reading makes the read/write split with its sibling obvious without opening either schema.

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?

'Only the fields you pass change; null clears one' tells the agent this is a partial update and how to erase a field, and 'list_sites shows each site's record' routes the read case elsewhere. It stops short of explicit when-not guidance (e.g. before vs. after checkout, or what happens if no record exists yet).

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