Skip to main content
Glama
Omnidim

@omnidim-ai/mcp-server

by Omnidim

listBulkCallLines

Read-only

Retrieve per-contact call results for a bulk call campaign, including call status, sent variables, and recording IDs. Page through results with a cursor and filter by status or exact phone number.

Instructions

Per-contact results for a campaign: what happened on each call, the variables you sent with that contact, and a pointer to the recording.

Paging

There is one rule. Call it with no cursor, then keep passing back the next_cursor you were handed until it comes back null.

cursor = None
while True:
    page = GET /lines?pagesize=150&cursor={cursor}
    handle(page["records"])
    cursor = page["next_cursor"]
    if not cursor: break

Each call returns a page of rows, oldest first: pagesize goes up to 150 and defaults to 30. Cursors are opaque, so pass back the string you were given and never build one. No contact is skipped or returned twice, even while the campaign is still dialing.

Transcripts are not in the row

Each row carries call.recording_id, not the conversation. Transcripts reach 212 KB, so carrying them here would make one page tens of megabytes. Fetch the one you want from GET /calls/logs/{recording_id}.

(Tags: Bulk calls)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoThe `next_cursor` from your previous response. Omit it on the first request. Opaque: pass it back unchanged.
searchNoAn exact phone number, matched against the contact's number and the number that called it. Not a substring search.
pagesizeNoRows per page. Above 150 the request is refused.
call_statusNoReturn only contacts in this state.
bulk_call_idYesId of the bulk call campaign.
include_totalNoAdd `total_records` to the response. It costs a count over the whole filtered campaign, so it is off unless you ask. Ask for it once to fill a header, not on every page of a walk.
interaction_statusNoReturn only contacts with this interaction outcome.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.11.1

TDQS

A4.4/5.0
Behavior5/5

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

The annotations only state readOnlyHint and openWorldHint, so the description carries the behavioral disclosure burden and succeeds. It explains the cursor contract, oldest-first ordering, exactly-once paging guarantees, why transcripts are not embedded, and where to fetch them. No contradiction with the 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 purpose is front-loaded and the rest is organized under clear Paging and Transcripts sections. The content is valuable, though some details repeat schema descriptions and the code block could be considered slightly redundant.

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 7-parameter paginated tool with no output schema, this description is complete: it covers the response shape, paging state machine, ordering, duplicate guarantees, and transcript retrieval beyond the endpoint. An agent has enough context to call and walk the endpoint correctly.

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 the baseline is 3. The description usefully reinforces cursor and pagesize behavior, but it does not add meaningful new semantics for search, call_status, interaction_status, bulk_call_id, or include_total beyond what the schema already documents.

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 opens with a specific and informative definition: per-contact results for a campaign, covering what happened on each call, variables sent with the contact, and a pointer to the recording. This clearly identifies the resource and distinguishes it from bulk-call-level or number-list-level sibling tools.

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 provides concrete usage context: this is the tool for per-contact campaign results, and it gives a complete paging loop plus an explicit pointer to a separate endpoint for transcripts. It does not name sibling tools or state exclusions, so it falls just short of full alternative-based guidance.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Omnidim/omnidim-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server