Skip to main content
Glama

getTaggedEntities

Retrieve Postman entities filtered by a specific tag. Requires an enterprise plan; returns 404 on other plans.

Instructions

Gets Postman entities by tag. Enterprise only - returns 404 on Free/Basic/Professional plans.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesTag ID
cursorNoPagination cursor
directionNoSort order
entityTypeNoFilter by entity type
limitNoMax entities to return

Implementation Reference

  • The GetTaggedEntitiesTool class implementing the 'getTaggedEntities' tool. Contains the handler logic: __init__ sets the tool name, get_tool_description defines the input schema (slug required, optional cursor/direction/entityType/limit params), and run_tool makes a GET request to /tags/{slug}/entities with optional query params.
    class GetTaggedEntitiesTool(ToolHandler):
        """Get tagged entities"""
        
        def __init__(self):
            super().__init__("getTaggedEntities")
        
        def get_tool_description(self) -> Tool:
            return Tool(
                name=self.name,
                description="Gets Postman entities by tag. Enterprise only - returns 404 on Free/Basic/Professional plans.",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "slug": {
                            "type": "string",
                            "description": "Tag ID"
                        },
                        "cursor": {
                            "type": "string",
                            "description": "Pagination cursor"
                        },
                        "direction": {
                            "type": "string",
                            "enum": ["asc", "desc"],
                            "description": "Sort order"
                        },
                        "entityType": {
                            "type": "string",
                            "description": "Filter by entity type"
                        },
                        "limit": {
                            "type": "integer",
                            "description": "Max entities to return"
                        }
                    },
                    "required": ["slug"]
                },
            )
        
        async def run_tool(self, args: dict) -> list[TextContent]:
            slug = args["slug"]
            params = {}
            if args.get("cursor"):
                params["cursor"] = args["cursor"]
            if args.get("direction"):
                params["direction"] = args["direction"]
            if args.get("entityType"):
                params["entityType"] = args["entityType"]
            if args.get("limit"):
                params["limit"] = args["limit"]
            
            result = await postman_api_call("GET", f"/tags/{slug}/entities", params=params)
            return [TextContent(type="text", text=json.dumps(result, indent=2))]
  • Input schema for getTaggedEntities. Defines 'slug' (required, string, tag ID), 'cursor' (optional, string), 'direction' (optional, enum asc/desc), 'entityType' (optional, string), and 'limit' (optional, integer).
    def get_tool_description(self) -> Tool:
        return Tool(
            name=self.name,
            description="Gets Postman entities by tag. Enterprise only - returns 404 on Free/Basic/Professional plans.",
            inputSchema={
                "type": "object",
                "properties": {
                    "slug": {
                        "type": "string",
                        "description": "Tag ID"
                    },
                    "cursor": {
                        "type": "string",
                        "description": "Pagination cursor"
                    },
                    "direction": {
                        "type": "string",
                        "enum": ["asc", "desc"],
                        "description": "Sort order"
                    },
                    "entityType": {
                        "type": "string",
                        "description": "Filter by entity type"
                    },
                    "limit": {
                        "type": "integer",
                        "description": "Max entities to return"
                    }
                },
                "required": ["slug"]
            },
        )
  • Registration of GetTaggedEntitiesTool() in the register_all_tools() function, which instantiates the handler for inclusion in the tool list.
    # Other
    GetTaggedEntitiesTool(),
    RunCollectionTool(),
  • The run_tool method execution logic: extracts 'slug' from args, builds optional query params (cursor, direction, entityType, limit), then calls the Postman API at GET /tags/{slug}/entities and returns the JSON result.
    async def run_tool(self, args: dict) -> list[TextContent]:
        slug = args["slug"]
        params = {}
        if args.get("cursor"):
            params["cursor"] = args["cursor"]
        if args.get("direction"):
            params["direction"] = args["direction"]
        if args.get("entityType"):
            params["entityType"] = args["entityType"]
        if args.get("limit"):
            params["limit"] = args["limit"]
        
        result = await postman_api_call("GET", f"/tags/{slug}/entities", params=params)
        return [TextContent(type="text", text=json.dumps(result, indent=2))]
Behavior2/5

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

No annotations are provided, so the description must disclose behaviors. It only states the read operation and a specific error condition. It does not describe pagination behavior (despite cursor and limit parameters), sorting, filtering effects, or any side effects. Minimal transparency.

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?

Two sentences with no redundancy. The purpose is front-loaded, and the Enterprise constraint is stated immediately. Every sentence adds value.

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 5 parameters, no output schema, and no annotations, the description is insufficient. It fails to explain that results are paginated, what entity types are included, or how to use cursor for pagination. Sibling tools suggest entity-specific retrievers, yet this tool's cross-entity nature is not clarified.

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?

The input schema has 100% description coverage, so the schema already documents each parameter. The description adds no additional meaning or context for parameters like slug, cursor, direction, entityType, or limit. Baseline score of 3 is appropriate.

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 clearly states the verb 'Gets' and the resource 'Postman entities by tag'. It also mentions the Enterprise-only limitation, which differentiates it from other get tools. However, 'Postman entities' is somewhat vague, lacking specificity about which entity types are returned.

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 indicates when NOT to use the tool (non-Enterprise plans) due to 404 error. It does not provide guidance on when to use this tool versus sibling tools like getCollection or getSpec, which return specific entity types. Implied usage but lacks explicit alternatives.

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/Sourav4670/postman-mcp'

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