Skip to main content
Glama
Sign In

ListPlus

by ai.listplus
OverviewDiscussionsAdmin

Send to a pipeline

send_to_pipeline

FREE (key) to hand over — records of a list shared with you go to one of the workspace's pipelines you may use (describe_list names them: HubSpot, Slack, lemlist …). The pipeline's data check and release apply: a manual one waits for a person; one that sends by itself delivers at once and its per-record price counts on this key's day budget. Up to 500 per call.

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": {
      "list_id": "<list_id>",
      "pipeline": "<pipeline>"
    },
    "name": "send_to_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoColumn → value: exact, { "contains": "…" }, { "not": "…" }, { "is_empty": true } or { "condition": "<one of filter_conditions>" }; ar_status by status name
list_idYesThe list's id (describe_list without list_id shows the lists shared with you)
languageNoLanguage of `tell_your_user` (default en)
pipelineYesThe pipeline's id or name (describe_list)
record_idsNoThe records' ids (`id` in query_records)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already establish that this is not read-only, is open-world, and is not destructive. The description adds meaningful behavior beyond that: manual pipelines wait for a person, automatic pipelines deliver immediately, per-record price counts against the key's day budget, and there is a per-call cap. It still leaves gaps around source-record handling and return behavior.

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 front-loaded with the core action and stays reasonably short. Some phrases such as 'FREE (key)' and 'data check and release' are dense or ambiguous, but there is little wasted text.

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?

For a five-parameter tool with a nested filter object and no output schema, the description covers purpose, pipeline discovery, timing, cost, and a cap. It does not explain what the tool returns, whether records are copied or moved, or how filter and record_ids interact. Those are meaningful gaps given the tool's complexity.

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

Parameters2/5

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

Schema description coverage is 100%, so the schema already documents all five parameters and the baseline would be 3. However, the description's 'Up to 500 per call' conflicts with record_ids having maxItems 1000 in the schema, which can mislead an agent about the actual batch limit. It also adds no clarity about filter versus record_ids selection.

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 states a specific action: records from a shared list are handed over to one of the workspace's pipelines. It also points to describe_list as the way to discover available pipelines. The informal phrase 'hand over' and lack of direct contrast with siblings like copy_records keep it from a 5.

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 implied by the statement that records of a list shared with you go to a workspace pipeline. The description also explains that pipelines may be manual or automatic, which helps set expectations. However, it does not explicitly say when to choose this tool over alternatives such as copy_records or create_trigger, nor does it state exclusions.

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

All ListPlus 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