Skip to main content
Glama

create_meta_campaign

Destructive

Set up Facebook and Instagram ad campaigns by specifying name, objective, and daily budget.

Instructions

Create a Meta (Facebook/Instagram) advertising campaign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCampaign name
objectiveYesCampaign objective
daily_budgetYesDaily budget in USD
Behavior2/5

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

The annotation `destructiveHint: true` is present, but the description adds no behavioral context beyond that. It does not disclose details such as auth requirements, rate limits, or the fact that the tool commits real ad spend.

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?

The description is a single sentence with no wasted words, but it could benefit from additional structure or elaboration without losing conciseness.

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 3 parameters, no output schema, and only a destructive annotation, the description fails to explain what the tool returns or how the campaign is configured beyond the listed parameters. It is incomplete for guiding the agent.

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 coverage is 100%, so the input schema already describes all three parameters. The description adds no additional meaning or context for the parameters, such as explaining the enum values or budget implications.

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 'Create' and the resource 'Meta (Facebook/Instagram) advertising campaign', distinguishing it from sibling tools for other platforms. However, it lacks any detail that differentiates it from other campaign creation tools within the same platform.

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 is provided on when to use this tool versus alternatives. The only implicit distinction is the platform name, but there is no explicit when/when-not context or mention of prerequisites.

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/jshorwitz/mcp-server'

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