Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

ce_delete_job

Delete an IBM Cloud Code Engine job by providing its name and project ID. Optionally specify the region.

Instructions

Delete a Code Engine job

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
job_nameYes
regionNo

Implementation Reference

  • Registration of the 'ce_delete_job' tool via server.tool() on the McpServer instance.
    server.tool("ce_delete_job", "Delete a Code Engine job", {
      project_id: z.string(), job_name: z.string(), region: z.string().optional(),
    }, async (p) => safeTool(async () => { w();
      await client.delete(`${base(p.region||r)}/projects/${p.project_id}/jobs/${p.job_name}`);
      return {message:"Job deleted"};
    }));
  • Input schema: requires project_id (string), job_name (string), and optional region (string).
    server.tool("ce_delete_job", "Delete a Code Engine job", {
      project_id: z.string(), job_name: z.string(), region: z.string().optional(),
  • Handler function: calls client.delete() to delete the job via the Code Engine API, then returns {message:'Job deleted'}.
    }, async (p) => safeTool(async () => { w();
      await client.delete(`${base(p.region||r)}/projects/${p.project_id}/jobs/${p.job_name}`);
      return {message:"Job deleted"};
Behavior2/5

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

No annotations exist, so the description carries the full burden. It does not disclose irreversible deletions, required permissions, or side effects. A destructive operation like this should include such behavioral context.

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?

At one sentence, it is very concise. However, it sacrifices informativeness for brevity; a slightly expanded version would retain conciseness while adding 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 that there are 3 parameters, no output schema, and no annotations, the description is insufficiently complete. It lacks usage guidelines, parameter descriptions, and behavioral notes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no parameter explanations. It fails to clarify what 'project_id', 'job_name', or 'region' represent, leaving the agent without necessary context.

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 Code Engine job' is a specific verb+resource pair. It clearly differentiates from sibling tools like ce_create_job, ce_run_job, and ce_list_jobs.

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. There is no mention of prerequisites (e.g., job must exist) or when not to use it.

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/ahmedselimmansor-ctrl/IBM_cloud_MCP_SERVER'

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