Skip to main content
Glama

Web2App market summary

get_web2app_market
Read-only

PAID ADD-ON «Web2App» (MCP comes with the annual plan). Summary of the web2app (quiz-to-paywall) advertising market from the Spytrend ad base: ads by brand, category, domain, page, country, language or month, with month range and filters. Without the add-on the call is refused; a monthly «site» subscriber is told that MCP access is part of the annual plan. QUOTA: 1 MCP credit per call (nothing for an account with a personal Web2App limit); summaries are not limited by the section row allowance. PAYWALL PRICES: every row of a brand, category, domain or page breakdown carries paywall — the prices of that row's funnels in the Spytrend Web2App library: funnels (walked funnels), priced_funnels, trial_funnels, currency, price_min / price_max / price_median (the plans in that currency), and latest — up to 3 latest priced funnels (funnel_id, host, geo, walked_at) with their plans (name, price, currency, period, intro_price, intro_period, full_price, trial_days, renewal_price, renewal_period, badge) or, when the plans were not parsed, screen_prices as written on the paywall screen. A row without paywall has no walked funnel yet. The prices are of the funnels, not limited by the month range. Quiz screens and screenshots are not in this answer: every row carries funnels_url — the funnels of that brand / category / domain / page / language in the Spytrend library, which the account owner opens on the site to view and download them. DATA: this is the Spytrend Web2App library. walked_at is the date the funnel's screens were captured; the country is only what geo says (empty geo = unknown, do not assume one); the funnel's length is steps_total / the screens returned — do not estimate them. PRICING: on paid plans ×1 after 500 MCP credits/month; one-time consent via accept_pricing_terms; before calling, get the maximum debit from estimate_cost (free) and tell the user.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_web2app_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNofree-text filter over brands and domains
toNolast month YYYY-MM
geoNoISO-2 countries (OR)
fromNofirst month YYYY-MM
brandNobrands (OR)
groupNobreakdown: brand (default), category, domain, page, geo, lang or month (the whole market as one row, a cell per month)
limitNorows, 1-100 (default 25)
categoryNoweb2app categories (OR)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / group / description
      Previous value: -"breakdown: brand (default), category, domain, page, geo, lang or month"New value: +"breakdown: brand (default), category, domain, page, geo, lang or month (the whole market as one row, a cell per month)"
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a read-only, non-destructive open-world read, and the description layers on material behavior: refusal conditions for non-subscribers, 1-credit quota per call with the personal-limit exemption, exclusion from the section row allowance, and the ×1 surcharge above 500 credits/month. It also disambiguates data semantics (walked_at is capture date, empty geo means unknown, funnel length is steps_total and must not be estimated), which no annotation conveys.

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?

Section headers (QUOTA, PAYWALL PRICES, DATA, PRICING) give useful structure, but the opening sentence is billing boilerplate rather than purpose, and the PAYWALL PRICES paragraph is a long enumeration of returned fields — including nested plan fields — that duplicates the output schema. Significant length is spent restating return shape instead of call guidance.

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?

For an 8-parameter, paywalled, aggregate read, the description covers the prerequisites, quota economics, consent flow and data-interpretation caveats an agent needs to call it correctly. Its main deficiency is that it over-explains return values already carried by the output schema, leaving the emphasis in the wrong place rather than omitting anything required.

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 baseline is 3, and the description earns above it by giving semantic rules the schema cannot: empty geo must be treated as unknown rather than assumed, and the group breakdown semantics (whole market as one row, a cell per month). It does not add syntax or interaction detail for brand/category/q beyond the schema text.

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 second sentence names a specific verb and resource — a market summary of the web2app (quiz-to-paywall) ad base — and enumerates the exact breakdown dimensions (brand, category, domain, page, country, language, month) plus the month-range and filter model. No sibling tool covers web2app market aggregation, so an agent can tell it apart from search_ads or get_ads_analytics without opening a 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?

It gives concrete call preconditions: it is a paid add-on, calls are refused without it, a monthly 'site' subscriber is told MCP is annual-only, and consent must be granted via accept_pricing_terms after checking estimate_cost. It also steers the agent away for screenshots (pointing to funnels_url opened on the site). It stops short of an explicit 'use this instead of X when Y' comparison against the analytics siblings.

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.