Skip to main content
Glama
Sign In
Superior Browser MCP

Superior Browser MCP

by SikandarMirza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

detect_ads

Detect ad elements on a webpage, optionally block them, and retrieve their positions and sizes.

Instructions

🆕 Detect ad elements on the page with detailed information

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

Input Schema

NameRequiredDescriptionDefault
blockAdsNoBlock detected ads (injects blocker)
includePositionsNoInclude ad positions and sizes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only says 'detect,' which implies a read-only operation, but the schema shows that setting blockAds=true injects a blocker, a potentially page-modifying side effect that is not disclosed. The description also doesn't mention permissions or what happens to the page after detection.

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?

The description is a single sentence, front-loaded, and contains no filler words. However, the phrase 'detailed information' is vague and could be more specific, slightly reducing the clarity per word.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description should explain what the tool returns (e.g., ad positions, sizes) and any side effects (e.g., blocking ads). It does neither, leaving the agent to guess the tool's full behavior. The schema covers parameters, but the overall contextual picture is incomplete.

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?

The input schema provides thorough descriptions for both parameters (blockAds and includePositions), achieving 100% coverage. The description adds no extra meaning beyond the schema, so the baseline score of 3 is appropriate.

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?

The description uses a specific verb ('detect') and resource ('ad elements on the page'), making the tool's core function clear. It is distinguishable from sibling tools like detect_popups and detect_captcha, though it doesn't explicitly highlight what makes it unique or what 'detailed information' entails.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of typical scenarios, prerequisites, or situations where another tool (e.g., browser_extract_content) would be more appropriate.

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

Deploy Server

Other Tools