Skip to main content
Glama
Sign In

Leadpoet

by com.leadpoet
OverviewDiscussionsAdmin

List follow-up tasks

listContactTasks
Read-onlyIdempotent

Lists the whole workspace's follow-up tasks on pipeline contacts, with no assignee, earliest due first, with the contact and company name and whether each is overdue. status is open (default), done or all. due_before (ISO 8601 with offset) keeps tasks due before that time; engagement_id keeps one engagement's tasks; company_card_id keeps one company's and lead_id one contact's. With lead_id it also returns that contact's engagement IDs, one per ICP, on one account when company_card_id is given. fields=count returns only the total. Tasks on a contact that left the pipeline are left out. Paged by page and limit.

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": "listContactTasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds real behavior: default status is open, results are ordered earliest due first, contacts who left the pipeline are excluded, and each row carries contact/company name and an overdue flag. It says nothing about permissions or result-size limits, but nothing essential is missing.

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?

Content is front-loaded on what the tool returns and how it is scoped, with no filler sentences. The middle filter sentence is a dense semicolon chain that is harder to scan than it needs to be.

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?

With no output schema, the description compensates by describing the returned row content, ordering, and count mode, and it explains pagination and pipeline-membership exclusions. An agent has everything needed to call it correctly, apart from the implicit query nesting already visible in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load, and it largely does: status values, ISO 8601 due_before, the three ID filters, and fields=count are all explained, including a non-obvious side effect where lead_id returns engagement IDs. The gap is that it never says these options live under a nested query object, and page/limit are dismissed with a single clause.

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?

"Lists the whole workspace's follow-up tasks on pipeline contacts" gives a specific verb and resource plus scope, ordering and returned fields. It is distinguishable from sibling tools like createContactTask, updateContactTask and listPipelineContacts without further reading.

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?

It states the default scope (whole workspace, no assignee filtering) and spells out what each filter selects, so an agent knows which call shape to reach for. It stops short of naming an alternative tool for a different use case, so there is no explicit when-not guidance.

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

All Leadpoet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources