Skip to main content
Glama

Postclick by PPC.io: Landing Page CRO and AI Page Builder

Save a note on an audit or design

save_note
DestructiveIdempotent

Uses no credits. Attaches anything you like to any record: who the client is, what they were charged, which findings they have already fixed, when you last sent them a report. Any name, any value. We never look inside it and the audit engine never reads it, so it cannot change what Postclick does. It is there so the work you do around these audits survives between conversations. Saving the same name again replaces it. Read them back with get_notes, and they also come back on the record itself.

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": {
      "subject_uri": "<subject_uri>",
      "key": "<key>"
    },
    "name": "save_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesYour own name for this field.
valueNoAnything: a string, a number, a list, an object.
subject_uriYesThe address of the thing this is about, like postclick://audit/<id>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds real context by explaining that re-saving a key replaces the previous value and that stored values are opaque and never read by the audit engine. It also discloses that the call consumes no credits, which directly matches the openWorldHint=false annotation. What it omits is what the save returns on success.

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?

Front-loads the cost signal ('Uses no credits') and keeps the key behaviors — arbitrary content, opacity, overwrite, retrieval route — in a short paragraph. Minor verbosity in the illustrative examples ('what they were charged… when you last sent them a report'), but nothing is genuinely wasted.

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 simple 3-parameter key/value store with no output schema and full annotation coverage, the description covers persistence, opacity, overwrite semantics, and read path. Only the save response shape is unaddressed, which is minor given there is no output 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 100%, so the baseline is 3, but the description adds meaning beyond the schema: values are arbitrary and unvalidated ('any name, any value'), and the key acts as an upsert identity ('saving the same name again replaces it'), which is not expressed anywhere in the schema.

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?

States a specific verb and resource — attach arbitrary key/value notes to any record, identified by a subject_uri — and the title narrows the scope to audits and designs. It is distinguishable from get_notes, though the description never explicitly contrasts itself with other write-side siblings.

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?

Gives a clear purpose context ('so the work you do around these audits survives between conversations') and explicitly routes reads to `get_notes`, plus notes that values also surface on the record itself. There is no explicit when-not-to-use guidance, but the use case is unambiguous.

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