For Agents
Manage Azure Media Services account-level filters that apply streaming-time track and time-range clipping rules across every Asset in a Media Services account.
Get started with Azure Media Services in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"create an Azure Media Services account filter"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Azure Media Services API.
Create or update an account-level filter on a Media Services account
List every account filter attached to a Media Services account
Retrieve a single account filter's track and presentation time properties
Update an existing filter's first quality, time range, or track selections
GET STARTED
Use for: I need to create an account-level filter on my Media Services account, List all account filters on a Media Services account, Retrieve a single account filter by name, Update the time range on an existing account filter
Not supported: Does not upload assets, run encoding jobs, or stream content — use for Media Services account-level filter management only.
Jentic publishes the only available OpenAPI document for Azure Media Services, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for Azure Media Services, keeping it validated and agent-ready. This slice of the Azure Media Services control plane manages account-level filters under Microsoft.Media/mediaServices/{accountName}/accountFilters. Account filters declare reusable streaming-time clipping rules — track selection, presentation time ranges, and timestamp filters — that Streaming Endpoints apply to every Asset under the account, so producers can ship the same on-the-fly trims across all assets without re-encoding. All requests authenticate with Azure AD OAuth 2.0 against Azure Resource Manager.
Delete an account filter that is no longer used
Patterns agents use Azure Media Services API for, with concrete tasks.
★ Reusable Clip Rules Across Assets
Producers ship the same streaming-time trim across every Asset in a Media Services account by defining an account filter once. The PUT on /accountFilters/{filterName} accepts presentationTimeRange, firstQuality, and trackSelections; Streaming Endpoints then apply the filter to manifest requests via filter query parameters, so producers do not re-encode assets to remove trailers or limit bitrates.
Create account filter 'no-intro' on Media Services account 'amsaccount' in resource group 'rg-media' with presentationTimeRange.startTimestamp=0 and presentationTimeRange.endTimestamp=600000000 (60 seconds in 100ns units).
Bitrate Floor Enforcement via firstQuality
When you want every player to start at a minimum bitrate, an account filter's firstQuality.bitrate sets the lowest manifest entry the Streaming Endpoint will return. Updating the value via PATCH (PUT replace) lets operators raise or lower the floor across the whole account without touching individual assets.
Update account filter 'min-bitrate' on account 'amsaccount' to set firstQuality.bitrate to 1500000 and verify via GET.
Filter Cleanup Before Account Decommission
Before removing or rebuilding a Media Services account, operators enumerate and delete any leftover account filters so reused filter names do not collide. The GET on /accountFilters lists all filters; DELETE removes them one at a time. This avoids stale filters being inadvertently re-applied if the account is recreated under the same name.
List account filters on 'amsaccount' and delete every filter whose name matches the prefix 'temp-'.
Agent-Driven Filter Audit
An AI agent through Jentic can enumerate account filters across Media Services accounts in a subscription, compare each filter's track selections and time ranges against a desired-state config, and queue PUT or DELETE calls to bring them into compliance. Jentic returns the per-filter operation schema so the agent never browses the Microsoft.Media docs.
List filters on every Media Services account in subscription '00000000-0000-0000-0000-000000000000' and report any without a presentationTimeRange.endTimestamp set.
5 endpoints — jentic publishes the only available openapi specification for azure media services, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/accountFilters
List account filters on a Media Services account
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/accountFilters/{filterName}
Create or update an account filter
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/accountFilters/{filterName}
Get an account filter by name
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/accountFilters/{filterName}
Patch an account filter's properties
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/accountFilters/{filterName}
Delete an account filter
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/accountFilters
List account filters on a Media Services account
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/accountFilters/{filterName}
Create or update an account filter
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/accountFilters/{filterName}
Get an account filter by name
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/accountFilters/{filterName}
Patch an account filter's properties
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD service principal credentials are stored encrypted in the Jentic vault. Agents receive short-lived Bearer tokens scoped to https://management.azure.com/ — client secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'create an Azure Media Services account filter') and Jentic returns the matching Microsoft.Media operation with its parameter schema.
Time to first call
Direct integration: half a day for Azure AD setup and filter CRUD wiring. Through Jentic: under 30 minutes — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Media Services Management Client
Manages the Media Services account, Streaming Endpoints, Transforms, and Jobs that consume these filters.
Use to provision the Media Services account and Streaming Endpoint that account filters apply to.
Azure Monitor Management Client
Configure metric alerts and diagnostic settings on the Media Services account.
Use to monitor Streaming Endpoint and encoding job health alongside filter management.
Azure Log Analytics
Centralise diagnostic logs from the Media Services account in a Log Analytics workspace.
Pair with this API to retain and query Streaming Endpoint and key delivery logs.
Specific to using Azure Media Services API through Jentic.
Why is there no official OpenAPI spec for Azure Media Services?
Microsoft Azure does not publish a single consolidated OpenAPI specification for the Microsoft.Media account filter control plane at this revision. Jentic generates and maintains this spec so that AI agents and developers can call Azure Media Services via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does this API use?
The API uses Azure Active Directory OAuth 2.0; agents acquire a token for the https://management.azure.com/ resource and pass it as a Bearer token. Jentic stores the service principal credentials in its vault and injects scoped tokens at call time.
Does this API let me upload videos or transcode assets?
No. This slice of the Media Services API only manages account-level filters. To upload assets, run encoding jobs, or stream content you call the Asset, Transform, Job, and StreamingEndpoint endpoints elsewhere in the Microsoft.Media control plane and the data-plane streaming URLs.
How do I create an account filter through Jentic?
Search Jentic for 'create an Azure Media Services account filter', load the resulting PUT operation on /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/accountFilters/{filterName}, then execute it with the filter name and presentationTimeRange or firstQuality body. Install with pip install jentic and run the async search-load-execute flow.
What is the difference between an account filter and an asset filter?
Account filters apply to every Asset in the Media Services account; asset filters scope to a single Asset. This API exposes account filters only — asset filters live under the Asset resource path of the broader Media Services control plane.
What are the rate limits for this API?
Azure Resource Manager applies subscription-level throttling — typically 12,000 reads and 1,200 writes per hour per subscription. Filter CRUD is light and rarely hits these limits in practice.
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/accountFilters/{filterName}
Delete an account filter