Skip to main content
Glama
zackscriven

ghl-mcp-server-v2

by zackscriven

ghl_email_legacy_campaign_list

Read-onlyIdempotent

List email campaigns from legacy schedules with filters for status, email status, and pagination.

Instructions

Legacy schedule/campaign listing (2021-era, distinct from the v3 campaign family at /emails/locations/{locationId}/campaigns/emails). Supports limit/offset pagination plus status and emailStatus filters. Get Campaigns Endpoint: GET /emails/schedule (Version header: 2021-07-28; source: emails.json) OAuth scopes: emails/schedule.readonly Pagination params: limit, offset — pass them to page through full result sets.

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 statusactive
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.
locationIdYesLocation ID to fetch campaigns from
emailStatusNoFilter by email delivery statuscomplete
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 campaign properties
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and no destructive effects. The description adds valuable behavioral context: it mentions pagination (limit/offset), filters (status, emailStatus), endpoint version, and OAuth scopes. This is more than what annotations provide.

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 structured well with front-loaded differentiation and endpoint details. However, the last sentence about pagination parameters is somewhat redundant given the schema, making it slightly less concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers key aspects: legacy status, endpoint, auth scopes, pagination, and filters. It does not describe the response format, but given no output schema and the tool's simplicity, this is acceptable. Annotations fill in safety details.

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 clear parameter descriptions. The description only summarizes that pagination and filters are supported, which adds minimal new meaning. Baseline of 3 is appropriate.

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 it is a 'Legacy schedule/campaign listing' from 2021-era, distinctly different from the v3 campaign family. It specifies the endpoint, OAuth scopes, and pagination parameters, making the purpose very clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly distinguishes this legacy tool from the v3 campaign family, providing context on when to use it. However, it does not directly compare with sibling tools like 'ghl_campaign_list' or 'ghl_email_list_campaigns', leaving some ambiguity for exact selection.

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