Skip to main content
Glama
Sign In
Agent.ai MCP Server

Agent.ai MCP Server

by OnStartups
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

youtube_social_content_render_social_report

Renders cross-platform social content into an HTML report with per-platform sections for organized analysis.

Instructions

Renders cross-platform social content as an HTML report with per-platform sections.

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": {
      "output_variable_name": "<output_variable_name>"
    },
    "name": "youtube_social_content_render_social_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_dataNo{{social_content}}
output_variable_nameYesresults_html

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description does not disclose behavioral traits like whether it is read-only, side effects, or dependencies. Only states it 'renders' without explaining what that entails.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence of 12 words is concise but lacks substance. It covers the basic purpose but misses important details that could be added without verbosity.

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 the tool has two parameters, no output schema, and many sibling render tools, the description is insufficient. It does not specify input format, output structure, or integration context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not explain the purpose or expected values of the two parameters (report_data, output_variable_name). Default values provide minimal hints but no explicit semantics.

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?

Description clearly states the verb 'renders', the resource 'cross-platform social content', and the output format 'HTML report with per-platform sections'. It differentiates from sibling render tools by specifying social content scope.

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 on when to use this tool versus alternatives like social_post_creator_render_post_report or social_performance_analyzer_render_analysis_report. Missing any context on prerequisites or exclusions.

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