update_pod
Modify pod configurations including status, credentials, and test information in Cisco API Gateway pod collections to maintain current operational settings.
Instructions
Update an existing pod in a collection. Can update status, credentials, test information, etc.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| collection | Yes | Collection name | |
| number | Yes | Pod number to update | |
| updates | Yes | Fields to update |
Implementation Reference
- src/index.js:152-180 (schema)Defines the input schema and metadata for the 'update_pod' tool, specifying required parameters: collection, number, and updates object.
{ name: 'update_pod', description: 'Update an existing pod in a collection. Can update status, credentials, test information, etc.', inputSchema: { type: 'object', properties: { collection: { type: 'string', description: 'Collection name', }, number: { type: 'number', description: 'Pod number to update', }, updates: { type: 'object', description: 'Fields to update', properties: { Status: { type: 'string' }, "Test Date": { type: 'string' }, "Test Status": { type: 'string' }, Password: { type: 'string' }, CRMPassword: { type: 'string' }, }, }, }, required: ['collection', 'number', 'updates'], }, }, - src/index.js:270-280 (handler)The MCP tool handler for 'update_pod' that extracts arguments and delegates to podsClient.updatePod, then formats the response as MCP content.
case 'update_pod': { const result = await podsClient.updatePod(args.collection, args.number, args.updates); return { content: [ { type: 'text', text: JSON.stringify(result, null, 2), }, ], }; } - src/podsClient.js:116-122 (helper)Core implementation of pod update: constructs API URL and sends PATCH request with updates payload using the configured auth headers.
async updatePod(collection, number, updates) { const url = `${this.baseUrl}/api/v2/pods/${collection}/${number}`; return this.makeRequest(url, { method: 'PATCH', body: JSON.stringify(updates), }); }