Skip to main content
Glama

Postclick by PPC.io: Landing Page CRO

Open one audit, design or report

fetch
Read-onlyIdempotent

Free. 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 the audit written up as prose instead, get_audit_report is the one you want. For a picture, take the asset_id off a field here and pass it to get_asset.

Input Schema

TableJSON 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.7/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds important output behavior: expand=* returns everything attached, long write-ups are withheld because they would exceed 100,000 characters, and each withheld item comes with its own address for later fetching.

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

Conciseness3/5

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

The opening is front-loaded and useful, but the description contains a redundant pair of sentences about get_audit_report: 'For the audit as finished prose...' and 'For the audit written up as prose instead...' say essentially the same thing. That repetition costs clarity in an otherwise informative description.

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?

There is no output schema, but the description compensates by explaining the return shape: attached items arrive with headline detail, long write-ups are withheld with fetch addresses, and available_links allows deeper exploration. For a four-parameter retrieval tool with complex expansion behavior, this is sufficiently complete.

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 schema already documents all four parameters. The description still adds useful semantics: uri format, bare id fallback, expand usage including `*`, and the practical reason to expand before fetching individual items.

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?

The description states a specific read/fetch operation over a single addressed resource, with concrete address examples like postclick://audit/<id>. It explicitly distinguishes this tool from get_audit_report and get_asset, so an agent can identify when this is the right retrieval primitive.

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?

It gives explicit guidance to use expand first, then fetch only the two or three items that matter. It also routes finished audit prose to get_audit_report and pictures to get_asset, naming the alternative tools and conditions.

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