Skip to main content
Glama

post_pvr_programmed

Create a new programmed recording on Freebox PVR: set channel, start/end timestamps, media storage, and optional conflict management.

Instructions

Create a new Precord ** Example request**: ** Example response**:

Error codes: noent, inval, inval_date_fmt, inval_end_before_start, system_time_incorrect, record_duration_too_long, record_date_in_past, unknown_channel, no_channel_svc, only_auto_disable, cannot_change_en_state, cannot_disable_has_data, internal_error, none, file_access_error, disk_full, private_but_no_private_dir, network_problem, resource_problem, no_stream_available, no_data_received, missed, stopped, unknown_error

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoprecord id
mediaNomedia name on which the record will be written to. See the Media API for more info. This property and can be empty when the file backing the record is not available, for example when secure is set.
pathNodestination directory on the media storage where the record will be written to
has_record_genNoif true, this precord has been generated using a Generator
record_gen_idNoif has_record_gen, this is the id of the generator
conflictNoif true this record may conflict with another record
overlap_listNoin case of conflict, this will contain the list of records id that may conflict with this record
enabledNoit only applies to generated records. If false the generated precord will be skipped.
alteredNoa precord is altered when some part of the recording may be missing. This can be the case if a conflict occurred during the recording (or connection was down)
stateNoValues: `disabled`: disabled; `start_error`: failed to start; `waiting_start_time`: scheduled; `starting`: starting; `running`: running; `running_error`: running with error; `failed`: failed; `finished`: finished
errorNo
channel_uuidNochannel uuid
channel_nameNooptional channel name
channel_qualityNo
channel_typeNoValues: `‘’ (empty string)`: auto; `iptv`: use only iptv streams; `dvb`: use only dvb streams
nameNorecord name
subnameNorecord subname
broadcast_typeNo
startNorecord start timestamp
endNorecord end timestamp
legacy_uriNoonly used for legacy apps. Use channel_uuid instead when available NOTE: only visible when called from player
force_channel_nameNoonly used for legacy apps. Use channel_uuid instead when available NOTE: only visible when called from player

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

The description only lists error codes but does not disclose any behavioral traits such as side effects, required permissions, or data validation rules. Since no annotations are provided, the description should detail these aspects.

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

Conciseness2/5

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

The description contains unhelpful placeholders like '** Example request**' and '** Example response**' with no actual content. The error code list is useful but poorly integrated, making the structure weak.

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?

With 22 parameters and no required fields, the description fails to explain what constitutes a valid request or how to construct it. The error code list is beneficial but does not compensate for the lack of usage 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 coverage is 86%, so most parameters have descriptions in the schema. The description does not add additional meaning or context for the parameters beyond what is already provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Create a new Precord', which identifies the action and resource, but 'Precord' is not clearly defined and could be ambiguous. It does not differentiate from other post tools or specify what is being created.

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 is provided on when to use this tool versus alternatives like put_pvr_programmed_id or get_pvr_programmed. There is no mention of prerequisites or typical use cases.

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/Nelson-PROIA/freebox-mcp'

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