Skip to main content
Glama
zackscriven

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_campaign_pause

Pause a running Facebook campaign by providing campaign ID and location ID. Stop active campaigns to control budget or adjust strategy.

Instructions

Pause campaign Pause a running Facebook campaign Endpoint: POST /ad-publishing/facebook/campaigns/{campaignId}/pause (Version header: 2021-07-28; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.write

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
campaignIdYesCampaign identifier
Behavior3/5

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

Annotations already indicate it's a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds OAuth scopes and endpoint details, and implies it only works on running campaigns, but does not explain error behavior or side effects. No contradiction with annotations.

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 concise with no unnecessary words. It includes title, action, endpoint, and scopes in a structured format. Minor redundancy from the title line, but overall efficient.

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 simple pause action, the description is mostly adequate. It lacks mention of prerequisites (e.g., campaign must be running), error conditions, and response format. No output schema or return value description is provided.

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?

Input schema has 100% parameter coverage with descriptions and examples for campaignId and locationId. The description adds no additional parameter semantics beyond what the schema provides, warranting the baseline score.

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?

The description clearly states 'Pause a running Facebook campaign', which is a specific verb and resource. The name and description together distinguish this from sibling tools like resume, delete, or duplicate by focusing on pausing a campaign.

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 description does not clarify that it only works on running campaigns or that other tools like 'ghl_ad_fb_campaign_resume' should be used to reverse the action.

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

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