Skip to main content
Glama
norman2112

Planview Portfolios Actions MCP Server

by norman2112

batch_create_tasks

Create multiple tasks in a single request to reduce latency. Handles partial success, returning successful tasks and failure details.

Instructions

[LOCAL — bulk write operation via SOAP. Beta MCP cannot create tasks.]

Batch create multiple tasks in a single SOAP call.

Much faster than calling create_task() multiple times. Creates all tasks in a single SOAP request, significantly reducing latency for bulk creation.

Args: tasks: List of task creation dictionaries. Each dict must contain: - Description: Task description (required) - FatherKey: Parent work entity key URI (required) Optional fields: Key, ScheduleStartDate, ScheduleFinishDate, Duration, etc. (same as create_task) options: Optional WorkOptionsDto dictionary (applies to all tasks)

Returns: Dict with per-task results (SOAP may partially succeed): - success: True only if all tasks succeeded - created: List of per-task entries in the same order as tasks: - description: task description (if available) - key: created task key (for succeeded tasks) or null (for failed tasks) - status: "success" | "failed" - error: present only for failed tasks - summary: {total, succeeded, failed} - warnings: optional list of warning messages

Raises: PlanviewValidationError: If task data is invalid PlanviewAuthError: If authentication fails PlanviewError: For other errors

Example: tasks = [ { "Description": "Task 1", "FatherKey": "key://2/$Plan/12345", "ScheduleStartDate": "2024-01-01T08:00:00", "ScheduleFinishDate": "2024-01-15T17:00:00" }, { "Description": "Task 2", "FatherKey": "key://2/$Plan/12345", "ScheduleStartDate": "2024-01-16T08:00:00", "ScheduleFinishDate": "2024-01-30T17:00:00" } ] result = await batch_create_tasks(tasks)

Notes: - All tasks are created in a single SOAP call, making this much faster than individual create_task() calls - If some tasks fail, this tool still returns the successful ones so callers can avoid retrying the already-created tasks (which would create duplicates) - Response fields may be null - this is normal SOAP API behavior - Use read_task() to verify individual tasks if needed - Recommended to use external Key (ekey://) to prevent duplicates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYesList of task dicts (each needs Description, FatherKey).
optionsNoOptional WorkOptionsDto for all tasks.
Behavior5/5

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

With no annotations, the description fully discloses behavior: bulk write via SOAP, partial success, null fields, error types. Covers success/failure handling and warnings. Provides detailed return schema and error classes.

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?

Well-structured with Args, Returns, Raises, Example, Notes. Front-loaded key info. Slightly long but each section earns its place. Could be tightened slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so description fully covers return values, errors, and partial success behavior. Provides enough context for correct usage, including edge cases like null fields and warnings.

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

Parameters5/5

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

Schema coverage is 100% but description adds significant value: specifies required fields (Description, FatherKey), optional fields, and provides a concrete example. Options parameter is explained clearly.

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 clearly states the tool's purpose: batch create tasks via SOAP, faster than individual calls. It distinguishes from siblings like create_task and batch_delete_tasks by emphasizing bulk creation and speed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (bulk creation for speed) and when not (Beta MCP cannot create tasks). Provides alternatives like create_task for single creation and read_task for verification. Includes caution about duplicates and external keys.

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/norman2112/portfoliosMCP'

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