IntuneRW-Core

Overview Schema Source Related Servers Discussions Admin

manage_intune_apps

Manage Intune mobile apps through CRUD, search, assignment, install-status, and staged EAM/Win32 lifecycle operations for deployment and troubleshooting.

Instructions

Manage Intune mobile apps — full CRUD, search, assignments and install status.

action values: list — List all mobile apps (top) get — Get app details + assignments (app_id) search — Search apps by display name (search_term) create — Raw Graph app registration (body); for complete EAM acquisition/ Win32 packaging use plan_lifecycle, not metadata-only creation. update — Update app metadata (app_id, body) delete — Delete an app (app_id, confirm=True) assign — Assign app to groups (app_id, body: {assignments:[...]}) remove_assignment — Remove one assignment (app_id, assignment_id, confirm=True) get_install_status — Get app install summary (app_id) list_discovered — List all apps discovered across managed devices get_mam_registrations — List managed app registrations (MAM enrollment) plan_lifecycle — Stage EAM-first acquisition/Win32 packaging (body). Required: app_name, publisher, version. No groups means CREATE ONLY. Optional: catalog_package_id; source {artifacts:[{filename,url,sha256}], scripts:[{filename,content}],setup_file}; win32 {description, install_command,uninstall_command,detection_path,detection_file, detection_version,architecture,minimum_windows_release,install_context}; evidence_urls. Use group_ids/group_names OR reuse_scope_from_app_id to propose assignments. Research official install instructions first. Never guess switches, versions or hashes. No tenant writes in planning. discover_deployment_scope — Read existing group assignments/filters/settings (app_id). Never invent a target or create groups without user confirmation. get_lifecycle_plan — Review immutable plan (plan_id); operator CLI approves exact digest. queue_lifecycle — Queue operator-approved plan (plan_id, plan_digest, confirm=True). Separate Windows worker performs writes. No inline packaging. get_lifecycle_job — Read durable worker result and partial-resource IDs (job_id).

Input Schema

Name	Required	Description	Default
`top`	No
`body`	No
`action`	Yes
`app_id`	No
`job_id`	No
`confirm`	No
`plan_id`	No
`plan_digest`	No
`search_term`	No
`assignment_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 21, 2026

TDQS

A4.6/5.0

Behavior4/5

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

No annotations are supplied, so the description must carry behavioral disclosure; it states confirm requirements for delete, remove_assignment, and queue_lifecycle, notes that planning performs no tenant writes, and explains that an operator-approved digest and separate Windows worker handle queued writes. It does not cover permissions/auth expectations, rate limits, or side effects of create/update/assign beyond the confirm gates.

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 long but justified by 13 distinct action values; the opening summary is front-loaded and the action list is organized as a compact reference. Each line generally earns its place by defining an action or a safety constraint.

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

Completeness4/5

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

For a complex multi-action tool with an output schema, the description covers the action surface, lifecycle planning safety, confirmation gates, and plan/job workflow. Remaining gaps are mostly fine-grained parameter formats and authentication context, which are secondary given the output schema and action-level guidance.

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

Parameters4/5

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

Schema coverage is 0%, so the description must explain the 10 parameters; it maps nearly every parameter to specific actions, including app_id, search_term, body, plan_id, plan_digest, job_id, assignment_id, confirm, and top. It gives useful body detail for assign and plan_lifecycle, but create/update body semantics remain vague and formats/defaults for app_id, search_term, and top are not elaborated.

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 first sentence names a specific resource (Intune mobile apps) and enumerates CRUD, search, assignment, and install-status capabilities; the action list then defines each operation. It also distinguishes metadata-only create from the broader plan_lifecycle path, helping an agent select the right operation.

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?

The action list explicitly maps each action to its purpose and key parameters, and it states that complete EAM/Win32 packaging should use plan_lifecycle rather than create. It adds concrete procedural guidance such as 'No groups means CREATE ONLY' and 'Research official install instructions first; never guess switches, versions or hashes.'

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