Skip to main content
Glama

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

Show the page designs

get_concepts
Read-onlyIdempotent

Uses no credits. Returns every concept rendered for an audit, each with its image URLs and a link to view it full size, and a runs.active count of how many are still rendering. A pack takes 3 to 8 minutes. While runs.active is above zero, call it with wait set to 300: it holds the connection open and comes back the instant a design lands, the stage moves, or the pack finishes, instead of returning the same half-empty list a dozen times in a row. A design landing is the thing worth interrupting for, and a wait gets it to the user within seconds of it existing. If a call comes back with nothing new, say nothing and call again — repeating a stage you already reported is worse than silence. A partial set is non-terminal: more images are still coming, so it is not the finished set. Some concepts may be flagged recommended, and often none is. The designs come back as pictures in the reply, not just links: without a concept_id it returns the opening screen of each so they can be compared, and with one it returns that single design as every band in page order, which is the whole page. Any figures, ratings or testimonials drawn into them are placeholders showing where real proof belongs, never the user's own data. To build, pass the recommended concept_id, or the first one when none is recommended: the user does not pick. If the user wants to SEND a design to anyone, use share_page with that concept_id: it gives back one public no-login page of the whole design. Never hand over an app or dashboard link for that, the recipient hits a login wall.

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": {
      "audit_id": "<audit_id>"
    },
    "name": "get_concepts"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoSeconds to wait for a material change. Use 25 for broad client compatibility; longer waits are available for hosts that support them. A timeout preserves the run; resume by ID instead of starting again.
audit_idYes
concept_idNoOptional. Given one, returns that design as its full stack of bands in page order instead of one opening screen per design.

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 read-only annotations, the description discloses that calls use no credits, packs take 3 to 8 minutes, waits hold the connection until a design lands or stage moves, partial results are non-terminal, and rendered figures are placeholders. It also explains that designs are returned as pictures in the reply rather than only as links.

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?

The definition is long but mostly front-loaded and every major clause carries operational detail needed for correct use. Some points, such as the importance of a design landing and the non-terminal nature of partial results, are elaborated more than strictly necessary.

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 fully covers the return shape: image URLs, full-size links, runs.active count, recommended flags, opening-screen versus full-page behavior, and placeholder content. It also explains what to do when results are partial or unchanged, leaving no major operational gap.

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?

The description adds operational meaning beyond the schema: wait=300 should be used while runs.active is positive, and concept_id changes the return from opening screens of each design to one design's full stack of bands. The audit_id scope is clear, though the schema coverage is already 67%.

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 resource and scope: it returns every concept rendered for an audit, including image URLs, full-size links, and a runs.active count. It also distinguishes the listing behavior from sharing via share_page and from building with a recommended concept_id.

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 when-to-use guidance: while runs.active is above zero, call with wait=300; use share_page when the user wants to send a design; and pass the recommended concept_id when building. These conditions and alternatives are directly actionable.

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