Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

ad_manager_fb_duplicate_ad

Duplicate a Facebook ad by providing its ad ID to create a copy within GoHighLevel's ad management, enabling quick replication for testing or variations.

Instructions

Duplicate ad

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adIdYes
Behavior2/5

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

Annotations indicate it's a write operation (readOnlyHint false), not idempotent, and not destructive, but the description adds no behavioral context such as what happens to the source ad, whether a new ad ID is returned, or if any settings are excluded. The bar is lower due to annotations but the description still contributes nothing.

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?

Two words is too terse – it's under-specification, not efficient conciseness. There is no explanation of scope, behavior, or parameters. While brevity is appreciated, this lacks critical information.

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?

For a mutation tool with no output schema and minimal annotations, the description is grossly inadequate. It doesn't say what happens after duplication, whether there are any constraints, how to handle errors, or what the expected result is. An agent has no confidence in calling this tool correctly.

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

Parameters1/5

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

The description does not mention the adId parameter at all. With 0% schema description coverage, the description must explain what adId refers to (e.g., 'the ID of the ad to duplicate') but it doesn't. The parameter is entirely undocumented.

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 states a clear verb ('Duplicate') and resource ('ad'), which distinguishes it from duplicating campaigns or adsets, but it lacks any detail about what duplication entails—whether it creates a new separate ad, copies all settings, or returns a new ID. It is more informative than a pure tautology but still minimal.

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?

There is no guidance on when to use this tool versus alternatives like upsert_ad, duplicate_adset, or delete_ad. No mention of prerequisites, the relationship to the original ad, or any caveats. An agent cannot infer when duplication is appropriate.

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

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