Skip to main content
Glama

Inspect a supplied social link

playground_external_link_inspect
Read-only

Fetch bounded metadata for an explicitly supplied HTTPS social-platform link. This does not watch its video or audio. Requires a creative-task grant because it invokes an external scraper. Returns source metadata, coverage, provenance and a content hash; it does not imply full video inspection.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTPS URL of the source to inspect or import; use the original source link.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.

Output Schema

NameRequiredDescriptionDefault
noteYes
contentYes
coverageYes
platformYes
sourceUrlYes
contentHashYes
retrievedAtNoSerialized ISO timestamp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, non-idempotent and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the external scraper invocation, the creative-task grant requirement, and the bounded nature of the fetch. It does not quantify the bound, disclose rate limits, or describe failure behavior, which keeps it from 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?

Three short sentences, front-loaded with the action and scope before prerequisites and return shape. Minor redundancy: 'does not imply full video inspection' restates the earlier 'does not watch its video or audio' and could be collapsed into one clause.

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?

With only two required parameters and an output schema present, the description covers purpose, prerequisite grant, external dependency, and result nature. What is missing is error/failure behavior for unreachable or unsupported links, which matters for an open-world scraper 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 description coverage is 100% for both parameters, so the baseline is 3. The description reinforces that the URL must be 'explicitly supplied' and be an original source link, but adds nothing about the required projectId or the URL's max length/format, which the schema already handles.

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

Purpose5/5

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

The description gives a specific verb and resource ('Fetch bounded metadata for an explicitly supplied HTTPS social-platform link') and immediately bounds the scope with two explicit negations ('does not watch its video or audio', 'does not imply full video inspection'). That contrast is enough to separate this from media-generation or import siblings without needing to name them.

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

Usage Guidelines4/5

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

It states the condition under which the tool applies (an explicitly supplied HTTPS social-platform link) and a prerequisite (a creative-task grant), and the 'does not watch' clause implicitly excludes using it as a video analysis step. It stops short of naming a concrete alternative for the excluded case, so it is strong but not complete routing guidance.

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.