Skip to main content
Glama
Amit-Lakhani

Postman MCP Generator

by Amit-Lakhani

update_activity_priority

Modify priority levels for Adobe Target activities to control execution order and resource allocation. Specify tenant and new priority values to adjust activity sequencing.

Instructions

Update the priority of an activity in Adobe Target.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tenantYesThe tenant identifier.
priorityYesThe new priority value for the activity.

Implementation Reference

  • The main handler function that executes the tool logic by making a PUT request to the Adobe Target API to update the priority of activity ID 168816.
    const executeFunction = async ({ tenant, priority }) => {
      const baseUrl = 'https://mc.adobe.io';
      const token = process.env.ADOBE_API_KEY;
      const apiKey = process.env.ADOBE_API_KEY;
    
      try {
        // Construct the URL for the request
        const url = `${baseUrl}/${tenant}/target/activities/ab/168816/priority`;
    
        // Set up headers for the request
        const headers = {
          'Authorization': `Bearer ${token}`,
          'X-Api-Key': apiKey,
          'Content-Type': 'application/vnd.adobe.target.v1+json'
        };
    
        // Prepare the body data for the request
        const body = JSON.stringify({ priority });
    
        // Perform the fetch request
        const response = await fetch(url, {
          method: 'PUT',
          headers,
          body
        });
    
        // Check if the response was successful
        if (!response.ok) {
          const errorData = await response.json();
          throw new Error(errorData);
        }
    
        // Parse and return the response data
        const data = await response.json();
        return data;
      } catch (error) {
        console.error('Error updating activity priority:', error);
        return { error: 'An error occurred while updating activity priority.' };
      }
    };
  • The JSON schema definition for the tool, including parameters for tenant and priority.
    definition: {
      type: 'function',
      function: {
        name: 'update_activity_priority',
        description: 'Update the priority of an activity in Adobe Target.',
        parameters: {
          type: 'object',
          properties: {
            tenant: {
              type: 'string',
              description: 'The tenant identifier.'
            },
            priority: {
              type: 'string',
              description: 'The new priority value for the activity.'
            }
          },
          required: ['tenant', 'priority']
        }
      }
    }
  • lib/tools.js:7-16 (registration)
    Dynamic registration of the tool via discoverTools, which imports apiTool from the tool's file path.
    export async function discoverTools() {
      const toolPromises = toolPaths.map(async (file) => {
        const module = await import(`../tools/${file}`);
        return {
          ...module.apiTool,
          path: file,
        };
      });
      return Promise.all(toolPromises);
    }
  • tools/paths.js:3-3 (registration)
    The toolPaths array entry listing the file path for the update_activity_priority tool.
    'adobe/adobe-target-admin-ap-is/update-activity-priority.js',

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
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 tool updates priority, implying a mutation, but fails to disclose critical traits such as required permissions, whether changes are reversible, potential side effects, or rate limits. This leaves significant gaps in understanding the tool's behavior.

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 is front-loaded with the core action and resource, making it highly concise and well-structured for quick comprehension.

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 complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, error handling, return values, and usage context, failing to compensate for the absence of structured data and leaving the agent under-informed.

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?

The input schema has 100% description coverage, with clear documentation for both parameters ('tenant' and 'priority'). The description adds no additional meaning beyond what the schema provides, such as explaining priority values or tenant context, so it meets the baseline for high schema coverage without enhancing parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Update') and the resource ('priority of an activity in Adobe Target'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'update_activity_schedule' or 'update_activity_state', but the focus on 'priority' provides implicit distinction.

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 like the sibling tools. The description lacks context about prerequisites, scenarios where priority updates are appropriate, or any exclusions, leaving the agent without usage direction beyond the basic function.

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