Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

List my contact imports

connections_import_list_runs
Read-only

List the member's own contact import runs, newest first. Each run shows its source (Google, CSV, LinkedIn export), status (running, succeeded or failed, with the reason code), start and finish times, and counts received, created, merged and skipped. Read-only. Use it to answer what was imported or whether an import finished.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many runs to return, newest first. Default 20, at most 100.
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
projectNoWorkspace to run this call in (id or name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / person
      Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[]
  4. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so "Read-only" in the description is largely redundant. The genuinely additive part is the field-level description of what each run record contains (source, status with reason code, start/finish times, received/created/merged/skipped counts), which substitutes for the absent output schema. However, nothing is said about pagination beyond the limit default, or about behavior when no runs exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the resource and ordering, followed by return-content detail and then usage purpose. Every sentence carries information an agent would otherwise have to infer, and there is no filler.

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

Completeness4/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 usefully summarizes the shape of each returned run, and the three optional parameters are fully covered by the schema. The only missing piece is how this tool relates to the import-starting siblings when an agent is deciding between reading and initiating imports.

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 description coverage is 100%, so the schema already explains limit (default 20, max 100), person impersonation, and project workspace scoping. The description reinforces the ordering semantics of limit ("newest first") but adds nothing about the person or project parameters, so the baseline of 3 applies.

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 and resource ("List the member's own contact import runs") and adds ordering ("newest first"), which clearly separates it from write-oriented siblings like connections_contacts_import_contacts or connections_import_google_contacts. It stops short of naming any sibling explicitly, so an agent must infer the read-vs-import boundary, but the scope is unambiguous.

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?

"Use it to answer what was imported or whether an import finished" gives concrete intent-based guidance for selecting this tool. It lacks an explicit exclusion statement (e.g., "do not use this to start an import; use connections_contacts_import_contacts"), which is the only gap for a sibling set that includes two import-starting tools.

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

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