Skip to main content
Glama
ohneben

ActiveCampaign MCP

retrieve_inaccessible_pipelines_by_user

Read-onlyIdempotent

Retrieve pipelines that a given user lacks access to. Useful for auditing user permissions.

Instructions

🟢 READ-ONLY · Deal Groups · GET /dealGroup/get_inaccessible_deal_groups

Retrieve inaccessible pipelines by user

Fetches data. Makes no changes to your ActiveCampaign account.

Retrieve pipelines that given user doesn't have access to

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results per page (ActiveCampaign default 20, max 100).
offsetNoZero-based offset into the result set for pagination.
ordersNoSort order as an object, e.g. {"email":"ASC"} → orders[email]=ASC.
userIdYesUser's Id
dealIdsYesDeal Ids Sent to ActiveCampaign as "dealIds[]".
filtersNoField filters as an object, e.g. {"name":"ecom"} → filters[name]=ecom.
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description reiterates 'Makes no changes' and provides the HTTP method (GET), which aligns but adds minimal new behavioral insight beyond 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 description is concise with a clear emoji prefix, endpoint, and two explanatory sentences. It is well-structured for quick scanning, though slightly redundant in repeating the purpose.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 6 parameters including nested objects and no output schema, the description does not explain return format, pagination behavior, or required parameter relationships. This leaves the agent with incomplete information for correct usage.

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% and each parameter has a clear description in the schema. The tool description adds no additional meaning or usage context for the parameters, so baseline 3 is appropriate.

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 uses specific verb 'Retrieve' and resource 'inaccessible pipelines', clearly distinguishing it as a specialized read operation for pipelines a user lacks access to. It also provides the endpoint path and category ('Deal Groups').

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 states the tool is read-only and fetches data, but does not explicitly guide when to use this tool over other pipeline-related tools in the sibling list. Some context is implied via the unique resource, but no exclusions or alternatives are provided.

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

Install Server

Other Tools

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/ohneben/ActiveCampaign-MCP'

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