Mediawork

Reviewed Jan 1, 2000.

• tools: 10 tools scanned
• metadata: scanned

No findings.

Tools (10)

• list_services

  The service categories vendors on Mediawork offer, such as Editorial, Sound Post or Visual Effects. Each has a uuid — pass it as `service` to search_facilities to filter the directory to vendors offering that service. Call this first when a question is about a kind of work.

• list_places

  Cities, states and countries that have at least one vendor listed, with a count of how many. Use a place `slug` as the `place` argument to search_facilities.

• search_facilities

  Search publicly listed post-production facilities, distribution vendors and creative companies. Filter by free text, by place slug (from list_places) and by service uuid (from list_services). To find vendors somewhere, prefer `place`; a `query` naming a place is treated as one anyway, and the response reports it as `resolvedPlace`. Results are paginated; when `hasMore` is true, call again with the returned `nextOffset`.

• get_facility

  The full public profile for one vendor: services offered, creatives on the team and what each of them does, production types, rooms and spaces, and addresses. Takes the `companySlug` and `facilitySlug` pair returned by search_facilities.

• search_faq

  Mediawork's published FAQ, grouped by category. With a query, returns matching questions and their answers; without one, returns every question so you can pick which to search for.

• list_blog_posts

  Published posts from the Mediawork blog, newest first. Use get_blog_post with a returned `slug` to read one in full.

• get_blog_post

  The full body of one published blog post, as markdown.

• get_plans

  Mediawork's subscription plans: what each includes, and its prices, plus `comparison`, a feature-by-feature table of every plan. Prices are published in several currencies — pass `currency` to return just one.

• search

  Search everything Mediawork publishes — vendor directory listings, FAQ entries and blog posts — and return matching records as {id, title, url}. Pass an `id` to `fetch` to read one in full. If your client supports them, the dedicated tools (search_facilities, search_faq, …) give richer, filterable results.

• fetch

  Retrieve the full contents of one record by the `id` returned from `search`.