Skip to main content
Glama
ejwhite7

@b2b-saas-inc/olli-mcp-server

create_campaign

Create a marketing campaign for social media with specified title, purpose, duration, platforms, and team assignments.

Instructions

Create a new campaign

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspace_idYesWorkspace slug or UUID
titleYesCampaign title
descriptionNo
purposeNo
statusNo
campaign_length_typeNo
campaign_duration_daysNo
start_dateNoISO 8601 date
end_dateNoISO 8601 date
platformsNoTarget platforms
tagsNo
team_idsNoTeam UUIDs to assign
product_idsNoProduct UUIDs to associate
assigned_user_idsNoUser UUIDs to assign
icp_idsNoICP UUIDs to associate
industry_idsNoIndustry UUIDs to associate
messaging_snippetsNoKey messages for this campaign
Behavior2/5

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

No annotations exist, and the description does not disclose any behavioral traits such as side effects, authentication requirements, or error conditions. For a mutation tool, this is insufficient.

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 extremely concise with no wasted words. It is front-loaded with the key action. However, for a tool with many parameters, a slightly longer description could be justified.

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's complexity (17 parameters, no output schema, no annotations) and many siblings, the description is too minimal. It lacks context about campaign creation, typical use cases, and relationship to other tools.

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 description adds no information beyond the input schema. With 17 parameters and only 65% schema coverage, the description should compensate for missing parameter details, but it does not.

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 'Create a new campaign' clearly states the action and resource. It is straightforward and aligns with the tool name, but does not differentiate from sibling tools like 'update_campaign' or 'campaign_generate'.

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, nor any prerequisites or contextual hints. The description is a single phrase without any usage direction.

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/ejwhite7/olli-social-mcp'

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