Skip to main content
Glama

ADS Beast

client_landing_scan

Read-only

Read a landing page and extract its headline, offer, selling points, calls to action, keywords and tone. Without url, the client's own site is used. AI: 1 AI request.

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

Input Schema

NameRequiredDescriptionDefault
urlNohttps:// page URL.
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description still adds two genuinely non-redundant behavioral facts: the cost signal ("AI: 1 AI request") and the fallback to the client's own site when url is omitted. It does not cover failure behavior or whether pages are JS-rendered, which keeps it off a 5.

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?

Two front-loaded sentences: capability first, default behavior second, with the cost noted tersely. The field list is long but each item is meaningful output content. Minor waste in the abrupt "AI: 1 AI request" fragment, but nothing is padded.

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 compensates well by enumerating the extracted fields, which effectively communicates the return shape. With annotations covering read-only safety and open-world access, the remaining gap is operational detail (rendering, failure modes) rather than anything blocking a correct call.

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 50%: url is documented in-schema but client_id has no description anywhere. The description usefully explains the url-omitted behavior, partially compensating, but leaves the relationship between client_id and url (e.g. does client_id pick the default site?) undefined. Baseline 3 is appropriate given partial coverage plus partial compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource ("Read a landing page and extract...") followed by an explicit inventory of what is extracted: headline, offer, selling points, CTAs, keywords, tone. An agent knows exactly what the output covers. It stops short of naming which sibling to prefer (e.g. aeo_visibility_scan), so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only routing-like statement is the default behavior "Without url, the client's own site is used," which is a fallback, not a when-to-use rule. There is no guidance on when to pick this over aeo_visibility_scan or client_market_analysis, and no exclusions or prerequisites. Usage is implied by the purpose rather than stated.

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.