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

Agent.ai MCP Server

by OnStartups
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

heygen_photo_avatar_render_avatar_report

Generates an HTML report showing the status of photo avatar creation.

Instructions

Renders photo avatar creation status as an HTML report.

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

Input Schema

NameRequiredDescriptionDefault
report_dataNo{{avatar_result}}
output_variable_nameYesresults_html

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only says 'renders a report' without stating whether it is read-only, whether it modifies state, or any permissions needed. The agent cannot infer if this is a safe read operation.

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

Conciseness2/5

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

The description is a single sentence, which is initially concise, but it is too terse for the information needed. It sacrifices necessary detail for brevity, making it under-specified rather than efficiently concise.

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

Completeness1/5

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

Given the lack of annotations, output schema, and parameter descriptions, the description fails to provide a complete picture. It does not describe the report content, format, or how it integrates into the Heygen avatar workflow, leaving critical gaps.

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?

The input schema has two parameters (report_data and output_variable_name) with 0% description coverage. The description does not explain what report_data should contain (e.g., the avatar creation result) or how output_variable_name is used. This omission leaves the agent without guidance on how to supply or capture data.

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 clearly states the verb 'Renders' and the resource 'photo avatar creation status as an HTML report', making the purpose understandable. However, it does not differentiate from many sibling tools that also render HTML reports (e.g., competitive_brief_render_brief_html, aeo_seo_research_render_research_report).

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 guidance on when to use this tool versus alternatives, nor any mention of prerequisites or context (e.g., that it should follow a photo avatar creation action). The description provides no usage conditions.

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