Skip to main content
Glama

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

Read my saved notes

get_notes
Read-onlyIdempotent

Uses no credits. Returns the notes saved against one record, or every note in the workspace when no address is given. Worth calling at the start of a repeat job, so a monthly report picks up whatever the last one left behind.

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

Input Schema

NameRequiredDescriptionDefault
subject_uriNoLimit to one record's notes. Leave it out for all of them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the description earns credit for adding what they cannot: that the call consumes no credits, and that omitting the address broadens the result from one record to the whole workspace. It does not warn about result volume or truncation when every note in the workspace is returned, which is the main remaining behavioral unknown.

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 short sentences, each doing work: cost, scope, and use case, in that order. The only friction is terminological drift — 'address' versus the schema's 'subject_uri' — which costs a moment of mapping but not comprehension.

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 one-parameter, read-only tool with a fully documented schema and rich annotations, the description covers what an agent needs: what it returns, how scope changes, and why to call it. It stops short of describing what a note looks like or how many may come back in the workspace-wide case, but no output schema exists to cover that either.

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 description coverage is 100% and the single parameter is fully documented, so the schema carries the load. The description restates the same scoping rule ('Leave it out for all of them') with the looser word 'address' rather than the schema's 'subject_uri', adding little meaning beyond 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 ('Returns the notes saved against one record') and immediately clarifies the two scopes: one record versus every note in the workspace. An agent can distinguish this from the sibling save_note on read/write grounds, though the description never names an alternative tool explicitly.

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 concrete when-to-use guidance: 'Worth calling at the start of a repeat job, so a monthly report picks up whatever the last one left behind.' That is a real usage context rather than an implied one. It does not state when not to call it, nor name a sibling to prefer for narrower retrieval.

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