Skip to main content
Glama
perforce

Perforce P4 MCP Server

Official
by perforce

modify_streams

Manage Perforce streams: create, update, delete, edit specs, and propagate changes between streams via copy, merge, integrate, or populate.

Instructions

Create/update/delete streams, edit/resolve/revert/shelve stream specs, copy/merge/integrate/populate between streams, switch workspace, create stream workspace (WRITE permission)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoHost restriction (create_workspace)
nameNoShort display name for the stream
rootNoWorkspace root directory (create_workspace)
forceNoForce operation
pathsNoStream view paths (e.g. ['share ...', 'isolate dir/...'])
quietNoSuppress informational messages (-q flag)
actionYesStream modification action: 'create'/'update'/'delete' a stream, 'edit_spec'/'resolve_spec'/'revert_spec'/'shelve_spec'/'unshelve_spec' for spec editing, 'copy'/'merge'/'integrate'/'populate' for propagation, 'switch' workspace stream, 'create_workspace' for a stream
branchNoBranch spec name for integrate/populate (-b flag)
parentNoParent stream (required for non-mainline create)
ignoredNoIgnored paths
optionsNoStream options: 'allsubmit/ownersubmit unlocked/locked toparent/notoparent fromparent/nofromparent'
previewNoPreview only, don't make changes (-n flag)
reverseNoReverse direction (-r flag)
virtualNoCopy using virtual stream (-v flag, copy only)
remappedNoRemapped paths
alt_rootsNoAlternate root paths (create_workspace)
max_filesNoLimit number of files processed (-m flag)
workspaceNoWorkspace name for switch
changelistNoChangelist for edit_spec, shelve_spec, unshelve_spec, or propagation, 'default' not allowed for edit_spec/shelve_spec/unshelve_spec
file_pathsNoFile paths for propagation
descriptionNoStream or workspace description
output_baseNoShow base revision with each scheduled resolve (-Ob flag for merge/integrate) or display list of files created (-o flag for populate)
parent_viewNoParent view treatment: 'inherit' or 'noinherit'
source_pathNoSource path for populate
stream_nameNoStream depot path (e.g. '//depot/main'). Also used as -S flag for propagation.
stream_typeNoStream type (required for create): mainline, development, sparsedev, release, sparserel, task, virtual
target_pathNoTarget path for populate
resolve_modeNoResolve mode for resolve_spec: 'auto', 'accept_theirs', 'accept_yours'
parent_streamNoOverride parent stream for propagation (-P flag)
workspace_nameNoWorkspace name to create (create_workspace)
target_changelistNoTarget changelist for unshelve_spec
skip_cherry_pickedNoSkip cherry-picked revisions already integrated (-Rs flag)
schedule_branch_resolveNoSchedule 'branch resolves' instead of branching new target files automatically (-Rb flag)
integrate_around_deletedNoIntegrate around deleted revisions (-Di flag)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided. The description mentions 'WRITE permission' but does not disclose side effects, destructive potential, or other behavioral traits. For a tool with many mutating actions (delete, force, reverse, etc.), this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that lists actions with commas. It is relatively concise but could be better structured (e.g., bullet points) to improve readability. No wasted words, but the list approach feels rushed.

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 tool's complexity (34 parameters, 14 action types, output schema present), the description is too sparse. It does not explain return values, prerequisites for actions, or common usage patterns. The agent needs more context to use this tool effectively.

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 coverage is 100%, so the schema already describes each parameter. The description adds minimal value beyond grouping actions; it does not clarify parameter interactions or provide usage examples. Baseline 3 is appropriate.

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 lists specific actions (create, update, delete, edit_spec, etc.) and resources (streams, workspace), making it clear what the tool does. It distinguishes from sibling query tools like query_streams by implying mutation. However, the list format is somewhat cluttered, and the phrase '(WRITE permission)' at the end adds context.

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 on when to use this tool vs alternatives (e.g., modify_workspaces for workspace creation). No when-not-to-use or prerequisite info. The description assumes the agent knows which action to pick.

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/perforce/p4mcp-server'

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