Skip to main content
Glama

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

Open one audit, design or report

fetch
Read-onlyIdempotent

Uses no credits. Reads any single thing by its address, which looks like postclick://audit/ and comes from search, from describe, or from any other tool's answer. A plain id works too if that is all you have. expand is what makes this worth calling: pass * and you get everything attached in one go, which for an audit means the findings, the buyers and their walkthroughs, the competitor scan, the copy rewrites and the designs. Each arrives with its headline detail; the long write-ups are marked as withheld with the address to fetch them from, because all of them together run to well over a hundred thousand characters and would swamp the answer. Expand first to see the shape, then fetch the two or three that matter. For the audit as finished prose, get_audit_report is one call and reads better than any of this. For a picture, take the asset_id off a field here and pass it to get_asset.

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

Input Schema

NameRequiredDescriptionDefault
idNoSource ID returned by search. Alias of uri for ChatGPT retrieval.
uriNoThe address, like postclick://audit/<id>. A bare id works too and will be looked up.
expandNoComma separated names of things to pull in with it, or `*` for all of them. Every answer lists what else is available under available_links, so you can always go deeper without guessing.
fieldsNoComma separated field names, when you only need a few. Left out, you get the useful ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses cost ('Uses no credits') and a non-obvious response behavior: long write-ups are withheld with addresses to fetch them, because the full set exceeds a hundred thousand characters. That truncation-plus-pointer mechanism is exactly the kind of trait an agent cannot infer from structured fields.

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-loaded with the highest-value constraint ('Uses no credits') and then the address format before the expansion advice. Dense rather than padded, though the middle sentence runs long and could be split; nearly every clause carries operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-shape burden and does: headline detail per item, withheld long write-ups with fetch addresses, and an available_links list in every answer. For a zero-required-parameter read tool of this complexity, an agent has everything needed to call it correctly and interpret the response.

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 earns more by showing what `expand` with `*` actually returns for an audit (findings, buyers and walkthroughs, competitor scan, copy rewrites, designs) and by explaining that every answer lists other options under available_links so deepening needs no guessing. That is meaning beyond the parameter's own definition.

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 ('reads any single thing by its address') and pins the address format with a concrete example, postclick://audit/<id>. It explicitly distinguishes itself from get_audit_report ('one call and reads better than any of this') and get_asset, so an agent can route 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 an explicit workflow ('Expand first to see the shape, then fetch the two or three that matter') plus named alternatives with the condition that selects them: get_audit_report for finished prose, get_asset for pictures. It also tells the agent where addresses come from (search, describe, any tool's answer) and that a bare id works when nothing else is available.

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