Skip to main content
Glama
Sign In
webEmbedding

webEmbedding

by jongko54
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

generate_embed_snippet

Read-onlyIdempotent

Generates ready-to-paste iframe embed snippets in HTML or Next.js for URLs verified to allow framing, producing accessible embed code for web pages or React components.

Instructions

Generate a ready-to-paste iframe embed snippet (HTML or Next.js) for a URL that is known to allow framing.

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

Input Schema

NameRequiredDescriptionDefault
urlYesURL to embed. It must allow framing; check with inspect_url first.
titleNoAccessible title attribute for the iframe.
frameworkNoSnippet flavor: html (plain iframe) or nextjs (React component).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.13
    • addedInput schema / properties / framework / description
      Added value: +"Snippet flavor: html (plain iframe) or nextjs (React component)."
    • addedInput schema / properties / title / description
      Added value: +"Accessible title attribute for the iframe."
    • addedInput schema / properties / url / description
      Added value: +"URL to embed. It must allow framing; check with inspect_url first."
  2. First observedv0.3.12

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine context beyond them: the output is a paste-ready snippet in one of two flavors, and framing permission is the caller's responsibility rather than something the tool verifies.

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 artifact, the two output flavors, and the key constraint — nothing redundant and nothing buried.

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 a three-parameter, side-effect-free generation tool with a fully documented schema and no output schema, the description covers what is produced and the framing prerequisite. It stops short of describing the returned snippet's structure or what happens if the URL disallows framing, but those gaps are minor.

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 all three parameters including the framework enum are already documented with meanings. The description's mention of 'HTML or Next.js' merely mirrors the framework enum and adds no syntax, defaults, or formatting guidance beyond the schema.

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?

States a specific verb and artifact: 'Generate a ready-to-paste iframe embed snippet (HTML or Next.js)'. No sibling tool produces snippets, so differentiation is implicit, but the description never names an alternative and relies on the reader to infer the boundary with inspect_url.

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 qualifier 'for a URL that is known to allow framing' implies a precondition and hints at a check-first workflow, but the description never names inspect_url as the prerequisite step — that routing only appears in the schema's url parameter description. Usage is implied rather than stated.

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