keyshade-mcp

Official

Overview Schema Source Related Servers Discussions Admin

list_secrets

Retrieve all secrets from a Keyshade project by providing the project slug. Supports pagination, sorting, search, and optional decryption of secret values.

Instructions

Lists all secrets within a specific Keyshade project

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectSlug": "<projectSlug>"
    },
    "name": "list_secrets"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (0-based)
`sort`	No	Sort field
`limit`	No	Number of items per page
`order`	No	Sort order
`search`	No	Search query
`projectSlug`	Yes	The slug of the project
`decryptValue`	No	Whether to decrypt secret values

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, pagination, or side effects. The schema hints at pagination and decryption, but the description omits these details.

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 a single concise sentence, front-loaded with purpose. It is efficient but could benefit from slightly more detail without being verbose.

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?

With 7 parameters, no annotations, and no output schema, the description is incomplete. It fails to explain pagination, filtering, sorting, or the decryptValue parameter, leaving the agent underinformed.

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond what the schema provides for the parameters.

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 tool lists all secrets within a specific Keyshade project. It uses a specific verb 'lists' and resource 'secrets', and the scope 'within a specific Keyshade project' distinguishes it from sibling tools like list_secrets_in_environment.

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?

No guidance is provided on when to use this tool versus alternatives, prerequisites, or when not to use it. The description only implies the scope but lacks explicit usage context.

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