Skip to main content
Glama

tools_remotion_src_onboarding_videos_meta_ads

Generate onboarding videos that demonstrate how to share Meta Ads assets to a partner Business for partner access.

Instructions

VIDEO 2 — Meta Ads partner access. Flow (share assets to a partner Business

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoKey-value arguments passed to the script via stdin
Behavior1/5

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

No annotations are available, so the description must carry the full burden of behavioral disclosure. It does not mention whether the tool is destructive, idempotent, requires authentication, or any side effects. The description is too vague to inform safe usage.

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 extremely short but incomplete, not concise. It is a single truncated phrase that does not form a complete sentence. Important information is missing, making it inefficient for an agent.

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 tool's complexity (likely generating a video asset for Meta Ads) and the absence of an output schema, the description provides virtually no context. It does not explain what the tool produces, any prerequisites, or how it interacts with the system. The description is wholly inadequate.

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

Parameters2/5

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

The input schema has 100% coverage for the single 'args' parameter, but the description adds no meaning beyond the schema. It fails to specify what key-value pairs are expected or what the values represent (e.g., video settings, partner ID). A higher score would require additional param guidance.

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

Purpose2/5

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

The description is fragmented and lacks a clear verb+resource pattern. It mentions 'VIDEO 2 — Meta Ads partner access' and 'Flow (share assets to a partner Business)' but does not explicitly state what the tool does (e.g., 'generates a video' or 'creates an asset'). The purpose is ambiguous compared to more descriptive sibling names.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. There are several sibling tools for different platforms (Google Ads, TikTok, etc.), but the description offers no criteria for selecting this one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/toggle-workspace/toggle-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server