Skip to main content
Glama
punkpeye

Postman MCP Generator

update_activity_schedule

Modify start and end times for Adobe Target activities using tenant-specific scheduling parameters to control campaign timing.

Instructions

Update the activity schedule in Adobe Target.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tenantYesThe tenant identifier.
startsAtYesThe start time of the activity in ISO 8601 format.
endsAtYesThe end time of the activity in ISO 8601 format.

Implementation Reference

  • The main handler function `executeFunction` that performs the HTTP PUT request to the Adobe Target API to update the activity schedule.
    const executeFunction = async ({ tenant, startsAt, endsAt }) => {
      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/schedule`;
    
        // 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 of the request
        const body = JSON.stringify({
          startsAt,
          endsAt
        });
    
        // 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 schedule:', error);
        return { error: 'An error occurred while updating the activity schedule.' };
      }
    };
  • JSON Schema defining the required input parameters for the tool: tenant (string), startsAt (ISO 8601 string), endsAt (ISO 8601 string).
      type: 'object',
      properties: {
        tenant: {
          type: 'string',
          description: 'The tenant identifier.'
        },
        startsAt: {
          type: 'string',
          description: 'The start time of the activity in ISO 8601 format.'
        },
        endsAt: {
          type: 'string',
          description: 'The end time of the activity in ISO 8601 format.'
        }
      },
      required: ['tenant', 'startsAt', 'endsAt']
    }
  • lib/tools.js:7-16 (registration)
    The `discoverTools` function dynamically imports the apiTool from each file in toolPaths (including this tool's file), spreading its properties to register the tool.
    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);
    }
  • The path to this tool's implementation file, listed in the toolPaths array used by discoverTools for registration.
    'adobe/adobe-target-admin-ap-is/update-activity-schedule.js'
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but only states it's an update operation. It doesn't mention permissions required, whether changes are reversible, rate limits, or what happens to unspecified schedule properties, leaving significant gaps for a mutation tool.

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, direct sentence with zero wasted words. It's appropriately sized for a simple update operation and front-loads the essential information efficiently.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like side effects, error conditions, or response format, which are crucial for safe tool invocation in this context.

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 parameters are fully documented in the schema. The description adds no additional meaning about the parameters beyond implying they relate to scheduling, which the schema already covers with ISO 8601 format details. This meets the baseline for high schema coverage.

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 resource ('activity schedule in Adobe Target'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings (update_activity_priority, update_activity_state) which also update activity properties, so it misses the highest clarity tier.

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 its siblings or alternatives. There's no mention of prerequisites, context, or exclusions, leaving the agent with minimal usage direction beyond the basic purpose.

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/punkpeye/mcpserveronline'

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