Skip to main content
Glama

get_suprsend_object_subscriptions

Read-onlyDestructiveIdempotent

List users subscribed to an object to find its followers or members. Returns paginated subscriber entries with optional channel preferences.

Instructions

List users / objects subscribed TO this object (its followers / members). Subscriptions are stored on the followed object.

When to use: the user asks "who follows project X?", "who's a member of organization Y?", or you need to enumerate an object's inbound subscribers.

When NOT to use:

  • For the inverse direction (what a user follows) — use get_suprsend_user_objects_subscriptions.

  • For mailing-list members — use get_suprsend_user_list_subscriptions on each user.

Returns: a paginated list of subscriber {type, id} entries. Set channel_preferences=true to also include each subscriber's channel preferences for this object. Default limit is 20.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_preferencesNoWhether to include channel preferences in the response. Default is false.
limitNoNumber of subscriptions to get for an object.
object_idYesThe object_id of the object's subscriptions to get.
object_typeYesThe type of object you want to get.
workspaceNoSuprsend workspace to get the object from.
Behavior1/5

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

The description claims this tool lists subscriptions (non-destructive), but the annotation `destructiveHint: true` marks it as destructive. This is a clear contradiction. The description does not disclose any destructive behavior, leaving agents confused about the tool's actual effects.

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 well-organized with clear sections, front-loads the core purpose, and every sentence adds necessary context without fluff.

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?

The description explains the return format and default limit, compensating for the lack of output schema. However, the annotation contradiction undermines overall completeness, and pagination details for navigating beyond the default limit are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with all parameters described. The description adds value by explaining the response shape (paginated list of subscriber {type, id}) and the effect of `channel_preferences`, which goes beyond the schema's boolean description.

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 clearly states the verb 'List' and the resource 'users / objects subscribed TO this object (its followers / members).' It distinguishes from sibling tools like `get_suprsend_user_objects_subscriptions` (inverse direction) and `get_suprsend_user_list_subscriptions` (mailing-list members).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly provides 'When to use' and 'When NOT to use' sections with specific alternative tools and scenarios, heavily guiding correct invocation.

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/suprsend/cli'

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