Skip to main content
Glama

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

Draw new page designs

generate_concepts

Draws design directions for an existing audit as rendered pictures. Only when the user asks to see designs: build_page needs none and sets the look itself. Use check_balance for page coverage and follow the user's permission. Returns a run to resume with get_concepts.

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

Input Schema

NameRequiredDescriptionDefault
countNoHow many distinct directions the user wants, up to 12. Leave it out for the standard pack of 2. Check returned page coverage before starting more work. Directions that already exist are counted and reused.
audit_idYes
directionNoOptional plain-English creative steer. Honoured above other design choices.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / count / description
      Previous value: -"How many distinct directions the user wants, up to 12. Leave it out for the standard pack of 2. Higher costs more, so quote the total back before agreeing to it. Directions that already exist are counted and reused, never bought twice."New value: +"How many distinct directions the user wants, up to 12. Leave it out for the standard pack of 2. Check returned page coverage before starting more work. Directions that already exist are counted and reused."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-read-only, open-world, non-idempotent behavior, so the description's job is to add context. It does: output is rendered pictures, the call produces a run object that is resumed via get_concepts, and the agent is told to verify page coverage before further work. It doesn't say anything about cost, wait time, or whether a partial run can be cancelled.

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?

Four short sentences, front-loaded with purpose and free of filler. The telegraphic style ("build_page needs none and sets the look itself", "follow the user's permission") is compact but slightly clipped enough to risk ambiguity.

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?

There is no output schema, and the description does explain the return shape at a high level (a run to resume with get_concepts), which is the key missing piece for a caller. Combined with the build_page and check_balance routing, an agent has enough to call it correctly, though permissions and failure behavior remain unstated.

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 coverage is 67%, so most parameters are already documented in the schema, and the description adds no extra meaning for audit_id, count, or direction. Count reuse semantics ("directions that already exist are counted and reused") appear in the schema, not the description, so the prose contributes nothing beyond structured fields here.

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 output ("Draws design directions for an existing audit as rendered pictures") plus scope (existing audit). It also explicitly contrasts itself with build_page, which "sets the look itself", so the agent can choose between them without opening either schema.

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 trigger ("Only when the user asks to see designs") and an explicit negative case with the alternative (build_page). It also routes coverage checking to check_balance. The one soft spot is "follow the user's permission", which is vague about what permission is required, but the when/when-not structure is genuinely present.

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