Skip to main content
Glama

github_secrets_delete

Remove GitHub Actions secrets to manage sensitive data in CI/CD pipelines and maintain repository security.

Instructions

Delete a GitHub Actions secret

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.js:1966-1995 (registration)
    Exact registration of the 'github_secrets_delete' MCP tool. Includes inline JSON schema for parameters (name, repo, env) and the async handler function that constructs and executes the 'gh secret delete' command using the shared runCommand helper.
      "github_secrets_delete",
      "Delete a GitHub Actions secret",
      {
        name: { type: "string", description: "Secret name to delete" },
        repo: { type: "string", description: "Repository (owner/repo format)", default: "" },
        env: { type: "string", description: "Environment name (optional)", default: "" }
      },
      async ({ name, repo, env }) => {
        const repoFlag = repo ? `-R ${repo}` : "";
        const envFlag = env ? `--env ${env}` : "";
    
        const result = await runCommand(`gh secret delete ${name} ${repoFlag} ${envFlag}`);
    
        if (!result.success) {
          return {
            content: [{
              type: "text",
              text: `Failed to delete secret!\n\nError: ${result.stderr || result.error}`
            }]
          };
        }
    
        return {
          content: [{
            type: "text",
            text: `Secret "${name}" deleted successfully.`
          }]
        };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action (delete) but lacks critical details: whether this requires specific permissions, if deletion is permanent, what happens on success/failure, or any rate limits. For a destructive operation, this is a significant gap in 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?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's front-loaded with the core action and resource, making it highly concise and well-structured for quick understanding.

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 the tool's complexity (a destructive operation), lack of annotations, and no output schema, the description is incomplete. It doesn't explain behavioral aspects like permissions, irreversibility, or response format, which are crucial for safe and effective use. The description alone is insufficient for this context.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is given since the schema fully covers the lack of parameters, and the description doesn't need to compensate.

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 'Delete a GitHub Actions secret' clearly states the specific action (delete) and resource (GitHub Actions secret). It distinguishes this tool from sibling tools like 'github_secrets_list' (list) and 'github_secrets_set' (set), making the purpose unambiguous and well-differentiated.

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?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. While it's clear this is for deletion, there's no mention of when deletion is appropriate compared to other secret management tools or what conditions must be met (e.g., existing secret).

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/rideRTD/RTD-DevOps'

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