Skip to main content
Glama
Sign In
Smartlead Simplified MCP Server

Smartlead Simplified MCP Server

by jonathan-politzki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

smartlead_get_campaign_sequence

Retrieve the sequence data for a specific campaign by providing its ID, enabling analysis of campaign workflows.

Instructions

Fetch a campaign's sequence data.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "smartlead_get_campaign_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYesID of the campaign to fetch sequences for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

The verb 'Fetch' implies a read-only operation, but without annotations, the description does not disclose behavioral details like return format, pagination, or whether it lists all sequences. It is minimally adequate for a simple read operation.

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 a single clear sentence, front-loading the purpose. It is appropriately concise with no wasted words.

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

Completeness3/5

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

Given the tool's simplicity (one parameter, no output schema, no nested objects), the description is minimally adequate. However, it lacks context about the structure or content of 'sequence data', which could aid an AI agent.

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% for the single parameter 'campaign_id', which is adequately described in the schema. The description adds no additional meaning beyond what the schema provides, meriting a baseline of 3.

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 'Fetch' and identifies the resource as 'a campaign's sequence data', clearly distinguishing from sibling tools like 'get_campaign' (general info) and 'get_campaign_sequence_analytics' (analytics). However, it lacks explicit differentiation statements.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as 'smartlead_get_campaign' or 'smartlead_get_campaign_sequence_analytics'. No context for exclusions or prerequisites is given.

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