Skip to main content
Glama
Wagner-Emden-IT-Services

placetel-web-api-mcp-server

List contacts

placetel_list_contacts
Read-onlyIdempotent

Fetch all Placetel account contacts with filters for name, company, email, phone number, and blocked status, plus pagination. Returns contact details in markdown or JSON.

Instructions

Fetch all contacts of the Placetel account. Supports field filters, number search and pagination. Read-only.

Returns a list of contact objects (id, first_name, last_name, company, phone/mobile numbers, email, tags, ...).

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
per_pageNoItems per page (max 100). Not honored by every endpoint.
filter_emailNoFilter by email (filter[email]).
search_numberNoSearch by phone number (search[number]).
filter_blockedNoFilter by blocked flag (filter[blocked]).
filter_companyNoFilter by company (filter[company]).
response_formatNoOutput format: 'markdown' (human-readable, default) or 'json' (machine-readable).markdown
filter_last_nameNoFilter by last name (filter[last_name]).
filter_first_nameNoFilter by first name (filter[first_name]).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the explicit "Read-only" sentence is largely redundant. The description does add value beyond annotations by sketching the returned contact fields (id, name, company, numbers, email, tags), which matters because no output schema exists, but it omits pagination defaults, total-count behavior and any rate limits.

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?

Two short sentences, with the core purpose front-loaded and the return shape second. The only wasted material is the "Read-only." fragment, which duplicates an annotation.

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 0 required parameters, full schema documentation and no output schema, an agent has what it needs: purpose, capability categories and a partial field list are all present. A complete definition would have enumerated the available filters and clarified whether response_format changes the returned shape.

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 every one of the 9 parameters is already self-documented, including the filter[x]/search[number] naming conventions and the per_page caveat. The description only restates the capability categories (filters, number search, pagination) at a higher level, adding little beyond the schema.

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?

"Fetch all contacts of the Placetel account" states a specific verb and resource, and the filter/search/pagination clause clarifies the listing scope. It does not explicitly distinguish itself from placetel_get_contact (single contact) or placetel_create_contact, so sibling differentiation is left implicit.

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?

The description implies a bulk-retrieval use case by mentioning filters, number search and pagination, which lets an agent infer it is for listing rather than fetching one record. However, it never names placetel_get_contact or placetel_create_contact as alternatives, nor states any when-not conditions.

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

Deploy Server

Other Tools