Skip to main content
Glama
Sign In
portkey-admin-mcp

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_egress_allowlist

Read-onlyIdempotent

Inspect the organisation's trusted custom-host egress allowlist and filter by domain to verify existing destinations before creating duplicates, without modifying entries.

Instructions

Inspect the organisation's trusted custom-host egress allowlist without changing destinations. Returns total and the current page of entries; filter by domain before creating duplicates, and use get_egress_allowlist_entry to inspect one entry. Requires organisation permission.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_egress_allowlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoSearch allowlisted domains
page_sizeNoItems per page, 1-100; Portkey defaults to 20
current_pageNoZero-based page number; the first page is 0

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv1.0.8

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so safety is covered; the description adds value by disclosing the return shape (total plus the current page of entries) and the organisation-permission requirement. It stops short of describing rate limits or error behavior, so it is strong rather than exhaustive.

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 dense sentences, zero filler, with the read-only guarantee front-loaded right after the resource. Every clause carries distinct information: scope, return shape, duplicate-check guidance, alternative tool, and permission requirement.

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

Completeness5/5

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

Given an output schema exists and annotations plus full schema descriptions cover mechanics, the description supplies exactly the missing pieces an agent needs: permission prerequisite, pagination/return expectation, and sibling routing. Nothing required to invoke it correctly is absent.

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%, so the schema already documents search, page_size, and current_page fully; baseline is 3. The description adds a small amount by framing the string parameter as a domain filter used for duplicate-checking, but says nothing about pagination parameters beyond 'current page'.

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?

States a specific verb ('Inspect') and resource ('organisation's trusted custom-host egress allowlist'), and immediately pins the scope as read-only ('without changing destinations'). It also names the singular sibling (get_egress_allowlist_entry), so an agent can distinguish it from get/create/update/delete_egress_allowlist_entry without opening any schema.

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?

Gives concrete when-to-use guidance: search by domain before creating entries to avoid duplicates, and switch to get_egress_allowlist_entry to inspect a single entry. It also states the prerequisite ('Requires organisation permission'), so both routing and access conditions are covered.

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