Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

emails_fetch_campaigns

Read-onlyIdempotent

Fetch email campaigns from GoHighLevel using filters like status, name, or pagination, and optionally include stats for delivered, opened, and clicked counts to measure performance.

Instructions

Get Campaigns

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter campaigns by name
limitNoMaximum number of campaigns to return. Defaults to 10, maximum is 100
offsetNoNumber of campaigns to skip for pagination
statusNoFilter by schedule status
archivedNoFilter archived campaigns
parentIdNoFilter campaigns by parent folder ID
showStatsNoWhen true, returns campaign statistics including delivered count, opened count, clicked count and revenue if available for the campaign. When false, returns campaign data without statistics.
locationIdNoLocation ID to fetch campaigns from Defaults to GHL_LOCATION_ID when omitted.
emailStatusNoFilter by email delivery status
campaignsOnlyNoReturn only campaigns, excluding folders
limitedFieldsNoWhen true, returns only essential campaign fields like id, templateDataDownloadUrl, updatedAt, type, templateType, templateId, downloadUrl and isPlainText. When false, returns complete campaign data including meta information, bulkRequestStatusInfo, ABTestInfo, resendScheduleInfo and all other campa
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is known. However, the description adds no behavioral context whatsoever—nothing about return format, pagination behavior, or what 'campaigns' refers to. With the low bar set by existing annotations, this still fails to add value.

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?

The description is a single short phrase, which is concise but severely under-specified. It lacks essential details about the tool's purpose, scope, or usage, making it more of an under-specification than a well-structured concise description.

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?

Given the complexity of 11 optional parameters and no output schema, the description is completely inadequate. It does not explain what the tool returns, what constitutes a campaign, or how to interpret the results. An agent would have no idea what to expect from calling this tool.

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%, with each of the 11 parameters having a descriptive entry. The description does not add any parameter semantics beyond the schema, so the baseline of 3 is appropriate.

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 'Get Campaigns' states a verb and resource but is extremely vague. It does not specify that these are email campaigns, nor does it distinguish this tool from the sibling 'campaigns_get_campaigns'. The tautological phrasing merely restates the tool name without adding clarity about scope.

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 zero guidance on when to use this tool versus alternatives. No mention of when the filtering parameters are useful, no exclusions, and no reference to similar sibling tools like campaigns_get_campaigns.

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