Skip to main content
Glama
Sign In

webEmbedding

by io.github.jongko54
OverviewDiscussionsAdmin

Discover Embed Candidates

discover_embed_candidates
Read-onlyIdempotent

Extract likely embed, preview, viewer, remix, and source URLs from a public or user-authorized page.

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": {
      "url": "<url>"
    },
    "name": "discover_embed_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic or user-authorized http(s) URL of the page to inspect.
timeout_secondsNoTimeout in seconds for fetching the page (1-30).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / timeout_seconds / description
      Added value: +"Timeout in seconds for fetching the page (1-30)."
    • addedInput schema / properties / url / description
      Added value: +"Public or user-authorized http(s) URL of the page to inspect."
  2. Added
  3. Removed
  4. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile needs no restating. The description adds one genuinely useful trait with "likely" — signaling heuristic, possibly imprecise results — but says nothing about network fetches, failure modes on unreachable pages, or result volume, which matters for a live-fetch tool.

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?

A single front-loaded sentence with the verb first and the enumerated resource types immediately following. Nothing is padded and nothing is repeated.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the input schema is fully documented. What is missing is the operational context an agent needs to pick this tool confidently over its siblings and to anticipate extraction being best-effort rather than exhaustive.

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 100%, so both url and timeout_seconds are fully documented in the schema and this hits the baseline. The description contributes no additional meaning about parameters, and in particular never hints that timeout governs a real network fetch.

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 ("Extract") plus a specific resource ("likely embed, preview, viewer, remix, and source URLs") from an input page, which tells an agent exactly what comes back conceptually. It does not differentiate itself from the adjacent inspect_url or generate_embed_snippet tools, so the boundary is inferable rather than stated.

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?

There is no when-to-use or when-not-to-use guidance. An agent choosing between discover_embed_candidates, inspect_url, and generate_embed_snippet gets no routing rule; the only constraint offered ("public or user-authorized page") is already stated verbatim in the url parameter schema.

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

All webEmbedding toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources