Skip to main content
Glama

List sequences

listSequences
Read-onlyIdempotent

List the email and LinkedIn sequences you can see (your team's shared ones and your own), most recently edited first, with step count and how many people are enrolled, active, opened, replied and interested.

Clera privately records this tool's inputs and results for usage tracking and support.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listSequences"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.

Output Schema

NameRequiredDescriptionDefault
sequencesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real value on top: sort order, the exact summary fields computed, and the visibility boundary. It also discloses that inputs and results are recorded for usage tracking and support, which an agent cannot learn from annotations.

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 first sentence is dense but front-loaded and well-ordered: resource, scope, sort, then returned metrics. The second sentence on data recording is somewhat boilerplate but does convey behavior, so it earns a place; only minor trimming is possible.

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

Completeness5/5

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

For a simple, single-optional-parameter read tool with an output schema and full annotation coverage, the description supplies everything an agent needs: what it lists, in what order, with what summary fields, and under what visibility constraint. Nothing material is missing.

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?

There is a single optional orgId parameter with 100% schema description coverage, including the 'only needed with multiple orgs' condition, so the schema already carries the meaning. The description adds nothing about the parameter, which is acceptable given full coverage but is only baseline.

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 names a specific verb (list) and resource (email and LinkedIn sequences), and pins down scope (team's shared plus your own), ordering (most recently edited first), and the summary metrics returned. An agent can distinguish this from the other list* siblings, which all target different resources, without opening any schema.

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?

Inclusion scope is stated (shared team sequences and your own), which implies when this tool applies, but there is no explicit when-not guidance or pointer to an alternative tool for a narrower query. Usable but leaves routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources