Skip to main content
Glama

Getfly CRM MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

List opportunities

getfly_list_opportunities
Read-only

List sales opportunities (deals in a campaign pipeline) with code, name, stage, probability, handler, customer and campaign. Filter by campaign with the campaign_code argument. GET /api/v6.1/opportunities.

Input Schema

NameRequiredDescriptionDefault
sortNoField to sort by (e.g. id, created_at, updated_at). Default: newest id first.
limitNoRecords to return, 1-100 (default 20).
fieldsNoComma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.
offsetNoRecords to skip (default 0). Pass the previous reply's next_offset.
filtersNoFilters as { "field": value } or { "field:operator": value }; operators eq, is, in, not_in, contains, between, not_between, gte, gt, lte, lt. in, not_in, between and not_between take an array. Examples: {"email:contains":"@acme.com"}, {"id:in":[1,2,3]}, {"created_at:between":["2026-10-01 00:00:00","2026-10-31 23:59:59"]}.
directionNoSort direction, used with sort (default asc).
campaign_codeNoOnly opportunities of this campaign (campaign code from getfly_list_campaigns).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds the endpoint and returned fields, but it does not describe pagination behavior, rate limits, authentication needs, or other operational traits.

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?

The description is front-loaded and compact: it states the resource, returned fields, campaign filtering, and endpoint in only a few sentences. There is no filler or repetition.

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?

There is no output schema, and while the description names some returned fields, it does not explain the response envelope, pagination behavior, or how next_offset should be used. The input schema fully covers parameters, but the description remains incomplete regarding return values.

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 documents all seven parameters, including filters, sorting, pagination, and campaign_code provenance. The description reinforces campaign_code and lists returned fields, but it adds little meaning beyond the structured 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?

The description states a specific verb and resource ("List sales opportunities") and lists the returned fields. It clearly identifies this as a list operation, but it does not explicitly distinguish it from sibling tools such as getfly_get_opportunity or getfly_list_campaigns.

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 list operation and the campaign_code filter, but there is no explicit guidance on when to use this tool versus get_opportunity or other opportunity-related siblings. It mentions campaign_code comes from getfly_list_campaigns, which is useful but limited.

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

All Getfly CRM MCP by usefulapi 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