Skip to main content
Glama
Alan7799DE

ClaudeMetaMCP

by Alan7799DE

crear_creative

Creates a Facebook ad creative from a Page: specify message, link, and image to get a creative ID.

Instructions

Crea el creative (contenido del anuncio) desde la Página de Facebook: mensaje + link + imagen. Devuelve creative_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkNoURL de destino.
nameYes
pageIdYesID de la Página de Facebook.
messageYes
imageUrlNoURL pública de la imagen.
descriptionNo
instagramUserIdNoPara que el anuncio también corra en la cuenta de IG.
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it creates a creative and returns an ID, but does not disclose behavioral traits such as permission requirements, side effects, or whether it modifies existing resources. Minimal transparency.

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?

The description is a single concise sentence that immediately conveys the core purpose and return value. No fluff, efficient for an AI agent to parse.

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

Completeness3/5

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

For a tool with no output schema, the description does mention the return value. However, given the complexity (7 parameters, no annotations), it lacks details on error conditions, parameter dependencies, or usage nuances. Completeness is adequate but minimal.

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?

The schema has 7 parameters with 57% description coverage. The description adds context by linking some parameters (message, link, image) to the tool's function, but does not explain parameters like description or instagramUserId beyond what the schema already provides.

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 it creates a creative (ad content) from a Facebook Page, specifying the components: message, link, image. It returns creative_id. Differentiates from sibling tools like crear_ad which create the whole ad, and other tools that manage campaigns or Instagram posts.

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 description specifies the source (Página de Facebook) and components, providing some context for when to use. However, it lacks explicit guidance on when to use this tool versus alternatives like crear_ad, or any prerequisites or exclusions.

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/Alan7799DE/ClaudeMetaMCP'

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