Skip to main content
Glama
morgenjacob-debug

Postman MCP Server

by morgenjacob-debug
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get elements by tag

getTaggedEntities
Read-onlyIdempotent

Get Postman entities by tag ID to search and organize workspaces, APIs, and collections that share the specified tag.

Instructions

Requires an Enterprise plan. Tagging is only available on Postman Enterprise plans. This tool returns a 404 error on Free, Basic, and Professional accounts.

Gets Postman elements (entities) by a given tag. Tags enable you to organize and search workspaces, APIs, and collections that contain shared tags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe tag's ID within a team or individual (non-team) user scope.
limitNoThe maximum number of tagged elements to return in a single call.
cursorNoThe cursor to get the next set of results in the paginated response. If you pass an invalid value, the API only returns the first set of results.
directionNoThe ascending (`asc`) or descending (`desc`) order to sort the results by, based on the time of the entity's tagging.desc
entityTypeNoFilter results for the given entity type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.12.3

TDQS

A3.7/5.0
Behavior5/5

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

尽管注解已声明 readOnlyHint=true，描述仍主动补充了关键行为：Enterprise plan 要求、各计划下的 404 错误行为，以及通过 tags 组织实体的语义。这种对失败场景的显式披露非常有价值。

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?

两段式结构清晰：首句突出企业版要求的警告，次句点明功能。所有企业版后续处理需求都在描述中，没有冗余信息。略失分在于缺少一个最终总结或示例。

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?

在注解和 schema 完整覆盖之余，描述又补充了企业版计划要求和错误行为等无法从结构数据推断的信息。作为一个简单的标签检索工具，这个描述已经相当完善，只缺操作示例。

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?

模式覆盖率为 100%，所有五个参数（slug, limit, cursor, direction, entityType）在 schema 中都有详细描述。描述本身未添加参数语义，但 schema 已足够完整、自解释，因此维持基线 3 分。

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?

描述明确使用动词 "Gets" 和资源 "Postman elements by a given tag"，并补充了'organize and search workspaces, APIs, and collections'的场景说明。虽然未显式区分兄弟工具，但资源范围清晰，足以让 agent 理解核心功能。

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

Usage Guidelines2/5

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

明确指出需要 Enterprise plan 及非企业版返回 404 的关键约束，这是重要的触发条件。但未提供何时选择其他兄弟工具（如 searchPostmanElements）的指导，也没有说明与按标签筛选、按关键词搜索等替代方案的区别。

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