Skip to main content
Glama

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

Who is bidding against this page

get_competitors
Read-onlyIdempotent

Costs nothing. Returns the competitor layer of a finished audit: the competitors bidding on the same clicks, the live ads Google is serving for each of them with the keyword, search volume and CPC behind every one, the landing pages those ads click to, which competitor advertises most, the advertisers currently on this page's own keyword, and the customer's own paid keyword count. The ad and keyword numbers are measured from the DataForSEO ads index, not written by a model, so they are safe to quote as figures. The competitor page summaries and the head-to-head read ARE written by the audit and are judgement, not measurement. Competitor page captures are attached where the scan reached them. Needs a completed audit. An audit that found nobody returns that plainly, which is a real answer and not a failure. Older audits carry no ad data at all. ask_audit with topic:competitors is the one for the written comparison; this is the one for the numbers. Safe to read again; it does not start new work.

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_competitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
audit_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantive behavior: it is free ('Costs nothing'), idempotent by re-read without launching work, may attach competitor page captures only where the scan reached them, and can return an empty competitor set as a valid answer. Crucially it separates measured data (DataForSEO ads index, safe to quote as figures) from model-written judgement (page summaries, head-to-head read), which prevents the agent from misrepresenting outputs.

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 fact ('Costs nothing') and then a dense enumeration where nearly every clause maps to a returned field. It is long and the middle sentence runs on, but trimming the field list would cost the agent real information about what comes back.

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 fully compensates by describing the return contents, their provenance (measured vs judgement), attachment behavior, and the empty-result case. Combined with the precondition and sibling routing, an agent has everything needed to call it correctly and interpret the output.

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 single audit_id parameter has 0% schema description coverage, so the description must carry the weight. It constrains which ID values are valid and useful: the audit must be completed, and older audits 'carry no ad data at all', implying the returned layer degrades by audit age. It does not state the ID format or where to get one (get_audit/list is not named), so it stops short of full coverage.

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 concrete resource and verb scope: 'Returns the competitor layer of a finished audit' and enumerates exactly what is in that layer (bidding competitors, live ads with keyword/SV/CPC, landing pages, top advertiser, keyword-level advertisers, own paid keyword count). It also names the sibling it is not, distinguishing itself from ask_audit's written comparison.

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 explicit preconditions ('Needs a completed audit'), explicit routing against an alternative ('ask_audit with topic:competitors is the one for the written comparison; this is the one for the numbers'), and edge-case guidance (an audit that found nobody returns that plainly; older audits carry no ad data). Also states it does not start new work, so the agent knows it is not a trigger for scanning.

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