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

ghl-mcp-server-v2

by zackscriven

ghl_email_get_workflow_campaign

Read-onlyIdempotent

Retrieve a single email workflow campaign by location ID and campaign ID to inspect its configuration and status.

Instructions

Get Workflow Campaign by ID Get a single workflow campaign by its ID Endpoint: GET /emails/locations/{locationId}/campaigns/workflows/{campaignId} (Version header: v3; source: v3/emails-v3.json) Requires a Sub-Account (location) token. OAuth scopes: emails/campaigns.readonly

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>",
      "campaignId": "<campaignId>"
    },
    "name": "ghl_email_get_workflow_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesCampaign ID
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 cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower, and the description still adds real context: it requires a Sub-Account (location) token, needs the emails/campaigns.readonly OAuth scope, and pins the v3 endpoint. It does not describe the returned payload, but that is the main remaining gap.

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 title line and verb line are front-loaded and redundant with each other, but the endpoint, auth, and scope lines all earn their place. Slightly duplicative wording keeps it from a 5.

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 simple two-parameter read tool with full schema coverage and no output schema, the description supplies auth requirements, OAuth scope, and the exact endpoint, which is enough for an agent to call it correctly. Only the shape of the response is left unstated.

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 both parameters are already documented, and the schema examples supply ID formats. The endpoint template in the description incidentally reveals that both are path parameters scoped to location and campaign, but there is no added guidance on formats or edge cases.

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?

The description uses a specific verb+resource ('Get a single workflow campaign by its ID') and the endpoint path confirms it fetches one workflow-type campaign within a location. It implicitly separates itself from list/campaign siblings by naming the distinct 'workflow campaign' resource, though it never names ghl_email_get_campaign or ghl_email_list_workflow_campaigns explicitly.

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?

Usage is only implied: you need a campaign ID to retrieve one workflow campaign. There is no explicit statement of when to use this instead of ghl_email_get_campaign or ghl_email_get_bulk_action_campaign, which are the closest siblings with near-identical names.

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