Skip to main content
Glama
Sign In
webEmbedding

webEmbedding

by jongko54
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

discover_embed_candidates

Read-onlyIdempotent

Inspect a public page to identify likely embed, preview, viewer, remix, and export candidates for integration.

Instructions

Extract likely embed, preview, viewer, remix, and export candidates from a 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 http(s) URL of the page to inspect, capture, or clone.
timeout_secondsNoTimeout in seconds for the static HTTP fetch of the page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.13
    • addedInput schema / properties / timeout_seconds / description
      Added value: +"Timeout in seconds for the static HTTP fetch of the page."
    • addedInput schema / properties / url / description
      Added value: +"Public http(s) URL of the page to inspect, capture, or clone."
  2. First observedv0.3.12

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered without help from the description. The word "likely" usefully signals heuristic, possibly incomplete results, and the schema's timeout parameter reveals the operation is a static fetch rather than a rendered capture. Beyond that, the description adds little about failure modes or result quality.

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?

A single front-loaded sentence with no filler; the enumerated candidate types do real work. It is arguably too terse for the amount of guidance an agent needs, but nothing is wasted.

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?

With two parameters (one required), no output schema, and full annotation coverage, the definition is close to sufficient. However, because there is no output schema, the description should say what a "candidate" looks like on return, and it should distinguish this discovery step from sibling inspection and snippet-generation tools.

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 description coverage is 100%, with url and timeout_seconds both documented in the schema, so the baseline of 3 applies. The description does not elaborate on either parameter, for example whether the URL must be publicly reachable for the static fetch to succeed.

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 names a specific verb ("Extract") and a specific resource ("likely embed, preview, viewer, remix, and export candidates from a page"), enumerating the candidate categories. It is clear what the tool does, though it never names a sibling such as inspect_url or generate_embed_snippet to differentiate itself explicitly.

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 facing inspect_url, audit_reference_url, and generate_embed_snippet has to infer that this tool is the heuristic discovery step that precedes snippet generation, and nothing in the description confirms or rules out that ordering.

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