Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_email_list_campaigns

Read-onlyIdempotent

List email campaigns for a location with pagination, status filtering, and name search.

Instructions

List Email Campaigns Get list of email campaigns for a location Endpoint: GET /emails/locations/{locationId}/campaigns/emails (Version header: v3; source: v3/emails-v3.json) Requires a Sub-Account (location) token. OAuth scopes: emails/campaigns.readonly Pagination params: limit, offset — pass them to page through full result sets.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "locationId": "<locationId>"
    },
    "name": "ghl_email_list_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of campaigns to return. Defaults to 10, minimum is 1, maximum is 20
offsetNoNumber of campaigns to skip for pagination. Defaults to 0, minimum is 0
searchNoSearch text for campaign name
statusNoFilter by campaign status
locationIdYesLocation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is low. The description adds real value beyond that: required token type, the emails/campaigns.readonly scope, endpoint version, and that limit/offset page through full result sets.

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?

Purpose is front-loaded in the first two lines, then supporting metadata follows. The endpoint/version/source line is dense but each line carries distinct operational info; no filler.

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?

For a read-only list tool with no output schema, the description covers authentication, scope, endpoint, and pagination mechanics. What it lacks is any hint about the response shape or the distinction from sibling list tools.

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%, so all five parameters (including the status enum and search) are already documented. The description only re-emphasizes the pagination pair and explains their purpose (page through full sets), adding marginal value over the schema.

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?

States a specific verb and resource ("Get list of email campaigns") scoped to a location, and even names the exact endpoint. However, it never distinguishes itself from siblings like ghl_email_legacy_campaign_list or ghl_email_list_bulk_action_campaigns, which an agent could easily confuse it with.

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

Usage Guidelines3/5

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

Provides prerequisite context ("Requires a Sub-Account (location) token") and OAuth scope, which helps confirm viability, but there is no explicit when-to-use guidance and no exclusions versus the legacy or bulk-action campaign list siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools