Skip to main content
Glama
clamp-sh

Clamp Analytics MCP Server

Official
by clamp-sh

search.landing_pages

Read-only

Identify landing pages that convert from organic search by combining Search Console clicks, impressions, and average position with actual conversions and sessions.

Instructions

The pre-click → post-click join: Search Console metrics per landing page, joined to what those organic-search visitors actually did. For each page that gets search traffic, returns clicks / impressions / average position (from Search Console) alongside organic_sessions and conversions (from Clamp's own data). This answers the question Search Console alone can't: not "which pages get search clicks" but "which search traffic actually converts".

The join is page-level by necessity — Google strips the search query after the click, so conversions attribute to the landing PAGE, not to a specific query. conversion_event defaults to "signup_completed"; set it to whatever event marks a conversion for this project.

Use for "which search pages convert", "are our top-ranking pages actually working", "where is search traffic leaking".

Examples:

  • "which pages get search clicks but don't convert" → read pages, find high clicks + low conversions

  • "do our docs pages convert organic search" → scan pages for /docs paths

  • "conversions from search on /pricing" → conversion_event set, find the /pricing row

Limitations: page-level only — query→conversion cannot be attributed (see above). Search Console pages are matched to Clamp landing pages by URL path, so pages differing only by query string may not line up. organic_sessions counts sessions whose ENTRY channel is organic search. Requires a connected Search Console property.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows to return (1-50). Defaults to 10.
periodNoTime period. Use "today", "yesterday", "7d", "30d", "90d", or a custom range as "YYYY-MM-DD:YYYY-MM-DD" (e.g. "2026-01-01:2026-03-31"). Defaults to "30d".
project_idNoTarget project ID (e.g. "proj_abc123"). Required when the credential has access to multiple projects. If omitted and only one project is accessible, that project is used automatically. Call `projects.list` to discover available project IDs.
conversion_eventNoEvent name that counts as a conversion. Default "signup_completed".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pagesYes
Behavior4/5

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

Annotations already indicate readOnlyHint=true. Description adds behavioral context: join nature, attribution constraints, default conversion event, and URL path matching. No contradictions.

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

Conciseness5/5

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

Description is thorough but well-structured: starts with core purpose, then details, examples, and limitations. Every sentence adds value.

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?

Given complexity of joining two data sources, description covers purpose, usage, parameters, examples, and limitations. Output schema exists, so return values are not needed.

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 covers 100% of parameters. Description adds meaning: explains default conversion_event and project_id requirement when multiple projects. Period and limit are also clarified.

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?

Clearly states it joins Search Console metrics with Clamp's organic_sessions and conversions to answer which search traffic converts. Distinct from siblings like search.queries.

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?

Explicitly states when to use (e.g., 'which search pages convert') and provides examples. Also notes limitations like page-level only and URL path matching.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/clamp-sh/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server